To:	Kimberley Burchett <OKRA AT max DOT tiac DOT net>
Cc:	DJGPP Mailing List <djgpp AT sun DOT soe DOT clarkson DOT edu>
Subject:	Re: combining .o files - nevermind
Date:	Sat, 15 Oct 1994 11:17:02 PDT
From:	"Marty Leisner" <leisner AT sdsp DOT mc DOT xerox DOT com>

In message <Pine DOT 3 DOT 89 DOT 9410142238 DOT A7963-0100000 AT max DOT tiac DOT net>you write:
>
>  I'm not so interested in making .a files anymore since I realized that 
>putting "*.o" on the command line works great.
>  Now I have a different question.  How can I make my library functions 
>so that I can redefine them?  For instance, the math library sin() can be 
>redefined in a program and it'll use the one you wrote instead.  But if I 
>have a function in my graph lib called WaitRetrace and I try to compile a 
>program that re-did WaitRetrace(), it'll error at linking.
>							Kim

I'm not quite sure what the problem is...

If you have small, modular files in a libary with very few entry 
points, you don't have a problem.

If you only have sin(), you can have the program do something else...

But if you combine sin() and cos() in the library, and you want
to call the library cos() and your sin(), you have a problem.

marty

- Raw text -