edler@JAN.ULTRA.NYU.EDU (Jan Edler) (06/13/89)
I'm looking at using the inline keyword. I'm playing with a version of gcc-1.35. I don't think a function declared inline should cause code to be emitted from cc1 to define its body. I.E., I think the current behavior of "static inline" should be the default for just plain "inline". If I have a large program, with many source files, and I put some inline functions into a .h file to be included by many .c files, I *MUST* use "static inline", to avoid a multiply-defined symbol complaint from the linker. This seems silly. I think just plain "inline" should be sufficient. Are there realistic cases where the current behavior of "inline" is preferable? Why not? Jan Edler edler@nyu.edu