🚀 go-pugleaf

In article <mwron-3010001520420001@c243286-a.bcreek1.mi.home.com>,
MWRon <mwron@metrowerks.com> wrote:

> In article <301020000939458133%hawkfish@spam.invalid>, Richard Wesley
> <hawkfish@spam.invalid> wrote:
> 
> >No, but this is widespread.  It broke GUSI something awful.  
> 
> I would not say MSL broke GUSI.
> If you have a car with 3 tires and someone learns if they sit a weight on
> one corner they can drive the car.  Then you put the 4th wheel on and it
> throws the balance off,  is that your fault.
> 
> >For some reason the idea of supplying a standard library that actually
> >exports the symbols in the standard library was not acceptable to our
> >friends at Metrowerks.  No idea why.
> 
> We are doing it right and if you tapped into Metrowerks non public
> undocumented headers and these change that is your own doing.

GUSI did not tap into non-public headers.  The problem is that the MSL
Pro6 public headers look like this (very roughly):

#if defined(__cplusplus)
inline int fopen (...) {return _fopen (...);}
#else
#define fopen _fopen
#endif

In other words, there is no actual fopen function, nor any way to
create one using the MSL headers - there is only a macro (or an inline
function).  So if you want to use the MW headers to link against a
different implementation provided by someone else, you are SOL, unless
you implement _fopen rather than fopen.  Maybe this is a accepted way
for MW to construct headers for standard libraries, but it sure isn't
very intuitive or useful for some of us.  And maybe this has something
to do with namespaces vs. C linkage (although given the simple aliasing
in the headers i can't see why), but it is sure a pain in the neck. 
Could we at least have an explanation of why this is being done this
way?

And please be careful casting aspersions upon GUSI.  GUSI's file date
functions work, which is more than I can say for the MSL libraries in
Pro 6.   Several folks, including me, have reported this here and to
MW.  stat is one specific example, but there are others.  At the
moment, CWCVS has an #ifdef for __MSL__ == 0x0600 to deal with this
problem.  The constant changes and bugs in these routines have been
driving me and the rest of the MacCVS team quite batty for years, which
is sort of ironic in light of Howard's boast here the other day about
expanding POSIX support in MSL.  

So IMHO, GUSI is not the only thing around here missing a wheel.  GUSI
has its own issues, but to paint MSL as some sort of perfect
implementation is just plain silly.

-- 
Richard Wesley           Electric Fish, Inc.    hawkfish@NeOlSePcAtMricfish.com

"Before we begin our banquet, I would like to say a few words.  And here they
 are:  Nitwit! Blubber! Oddment! Tweak!" - "Harry Potter & Philospher's Stone"