Re: Re[2]: [Mingw-users] missing ISO C89/C99 functions in runtime

[SONE T. <ts...@cm...>]

On Tue, Dec 05, 2000 at 12:33:15PM -0800, Earnie Boyd wrote:
> --- Paul Sokolovsky <pa...@is...> wrote:
> >     My HO if it's separate library (not just proxy), it is worth a
> > better name. What about libc.a ? ;-)
> Too confusing.  It wouldn't be complete. MSVCRT is the libc.  These are newly
> added additions to the standard so libnewname.a is definitive.

Remember, lib[mc]oldname.a is a _import_ library for MSVCRT.DLL/CRTDLL.DLL,
which adds extra '_' to symbols.

I assume you are to create a new _import_ library for MSVCP60.DLL, because
of the name 'libnewname.a'.
This will cause another runtime problem, which is worse than MSVCRT/CRTDLL
issue, because MSVCP60.DLL is more likely to change, and does not come
with most versions of Windows (I think WinMe is the only one with
MSVCP60.DLL builtin).
I'd name it 'libmsvcp60.a' in this case, and not put it in specs,
so that user is notified that the program requires special runtime DLL.

If you create a new _static_ library from PD source, the name
'libnewname.a' is confusing.  It better simply go into libmingw32.a.

-- 
Takeshi