Mail Archives: djgpp-workers/1999/06/08/15:06:49
[For those of you just joining us: we're talking about new math
routines found at ftp://ftp.delorie.com/private/from_erudd.zip - DJ]
> There are a number of routines that are non-reentrant. If it is
> important for them to be reentrant, I will have to fix them.
The issue of libc reentrancy came up recently. It doesn't make sense
to create new non-reentrant functions if we know people are concerned
with reentrancy.
> > 8) I understand that we need to keep the old version of modfl, since
> > there's no new one, right?
>
> This is a long double (non-ANSI) routine. I don't know why the old
> libc had it, since practically no other long double routines were
> furnished. For compatibility, we should retain it, however.
printf needs it for long double support, I think.
> I had a discussion with DJ about the necessity for stubs; I have to
> go back and look that over again, since I didn't entirely understand
> the need for them.
Stubs are needed when a function defined by one spec calls a function
that isn't defined by that spec. For example, if printf() calls
modfl(), and printf() is ANSI but modfl() violates ANSI, then we
replace modfl() with __modfl() (which is OK with ANSI) and create a
stub called modfl() that simply calls __modfl(). That way, using
printf() won't pollute your ANSI namespace with other functions,
because now it's only calling __modfl().
- Raw text -