On Thu, 21 Jun 2001 [EMAIL PROTECTED] wrote:
> If you write functions that are named like the original ones, you may
> get into problems with two points:
>
> 1) other functions from libc may use implementation specific
> details and force to have both implementations probably
> working against each other or detroying data structures.
That is exactly what's happening now with GCC 3.0 and your printf
replacement... The implementation-specific details in the system's
stdio.h conflict with your printf().
> If you name it differently, you may include the system's stdio too, but
> then you may not call any of your functions the same as they are called in
> stdio.h
Well, the point was to avoid the system's stdio. Your printf
implementation includes the system's stdio.h and provides a printf()
implementation. So your code does not conform to the statement you
just made.
Eric
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
