Joerg Schilling <[EMAIL PROTECTED]> wrote:
> If you decide to have your own stdio.h, it should be POSIX compliant.
> Unfortunately, stdio.h relies on many implementation specific stuff like
> the local stdio package as well as on POSIX oddities. Believe me, it's
> close to imposible to do this with stdio.h in a portable way.
What I don't see is the benefit of using procedure names which are the
same as defined names, when a name change will allow the same
well-behaved functionality without possible conflicts. Writing a stdio
package is HARD, but trying to avoid conflict with all implementations
while using the same names seems to add to the dificulties without
benefit, and certainly leaves you open to having the standard change in
the future.
Having written just printf() back in per-ANSI days, when K&R was all
the standard there was, I can appreciate just how much work goes into
getting all the cases right, even back before long long, long double,
etc. On the other hand, Joerg doesn't have to avoid all internal buffers
(memory is expensive) and make float formats usefully fast on a 2MHz
8080. But even then I decided that using a non-conflicting name was the
best solution, and it a user then wanted to
#define printf TAprintf
that was fine, I didn't cause the problem.
--
-bill davidsen ([EMAIL PROTECTED])
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
