Hi Shane, nesC aggressively inlines over the whole program, and all functions are implicitly marked as inline. Only the biggest function remain as functions. In fact, it's actually very difficult to tell nesC *not* to inline a function in those rare cases that you may think you don't want inlining.
Cory On 3/31/06, Shane B. Eisenman <[EMAIL PROTECTED]> wrote: > Aside from defining the external interfaces of a component, nesC > *interfaces* provide a nice way to logically group related functions > within a module even when it would suffice to implement a local function. > However, some such functions might be very small, e.g., just act on a few > variables and return, and might normally be defined as *inline*. Is there > a way to define an interface function as inline? Or perhaps ncc/gcc is > smart enough to optimize on it's own? > > -shane > ------------------------------------ > http://www.comet.columbia.edu/~shane > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > _______________________________________________ Tinyos-help mailing list [email protected] https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
