This is the mail archive of the egcs@egcs.cygnus.com mailing list for the EGCS project. See the EGCS home page for more information.
At 09:02 PM 2/12/99 -0500, you wrote:
>Or you can isolate the inline functions in their own header file, and
>have a separate C file that just does
>
>#define inline /* nothing */
>#include <linux/inlinefuns.h>
>
>No code duplication, and if all the inlines went through, the linker
>will throw away the unnecessary object module.
That same technique might be usable to remove the code duplication wart
with libc. The object module generated goes in libc.a; the linker will
ignore it if all the functions used inlined.
For dynamic linked implementations, the object module goes in libc.so and
the dynamic linker will ignore it.
--
.*. "Clouds are not spheres, mountains are not cones, coastlines are not
-() < circles, and bark is not smooth, nor does lightning travel in a
`*' straight line." -------------------------------------------------
-- B. Mandelbrot |http://surf.to/pgd.net
_____________________ ____|________ Paul Derbyshire pderbysh@usa.net
Programmer & Humanist|ICQ: 10423848|