> No by the time we have apps, the names of static functions are long gone. > What source means is the same .c (or .cpp if you insist on that sort of > thing) file. For example, let's say you have two source files Not entirely true with the CW default settings. Almost all PRCs built with CW that I have looked at include all of the function names. This is a really stupid setting in CW since it is useless on the PC. HOT TIP: You can reduce your PRC size by 10-15% by setting MacsBug Symbol to None. Scott Maxwell
- Re: why we use static before a function what is the signif... Eric VERGNAUD
- Re: why we use static before a function what is the s... Gaurav Palvia
- Re: why we use static before a function what is the s... Greg Winton
- RE: why we use static before a function what is the s... Richard Hartman
- Re: why we use static before a function what is the s... Mike Davis
- RE: why we use static before a function what is the s... Neil Brown
- Re: why we use static before a function what is the s... dean
- RE: why we use static before a function what is the s... Scott Maxwell
- RE: why we use static before a function what is the s... Yu, Ken
- RE: why we use static before a function what is the s... Greg Winton
