Subject: Re: DocBook function synopsis From: Graydon Hoare <graydon@xxxxxxxxxxxxx> Date: Fri, 10 Jul 1998 11:51:55 -0400 |
> > This is definitely an implementation concern. You don't need to know > > whether a method is inlined or not to be able to use it correctly. > > Given a least-common denominator approach, "inline" would certainly appear > to be excluded as purely a C++ concern of space/time tradeoff and debug-ability > which would only be of interest to C++ customers. erm, inline functions are significant to anyone using an API. They are unlinkable, and can create weirdness in an inheritence hierarchy. I think it's worth letting an API reader know something is inline, rather than tear their hair out. -graydon DSSSList info and archive: http://www.mulberrytech.com/dsssl/dssslist
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: DocBook function synopsis, Mitch C. Amiano | Thread | Re: DocBook function synopsis, Mitch C. Amiano |
Re: DocBook function synopsis, Mitch C. Amiano | Date | RE: DocBook function synopsis, Graydon Hoare |
Month |