Re: [cc65] Problems with va_copy

Hi!

On Sun, Dec 11, 2005 at 05:48:14PM +0100, Spiro Trikaliotis wrote:
> Wasn't there some version of gcc where many standard include files were
> mangled into just one include file? Thus, if you included either of
> them, it just included the generic one, which made all names, even the
> ones which should not have been included? Ok, this is not exactly the
> same, although the namespace is polluted with names it should not have
> been.

You aren't allowed to use most standard identifiers, regardless of the
included header files, so this is not a real problem. For example, you are not
allowed to name a function "printf", even if you do not include stdio.h.

> Additionally, I remember some version of the Microsoft Compiler
> including windows.h if some of the standard header were included. :(

Without facts this is hard to believe. Even for me, who believes that anything
evil may come from the Great Dark at Redmond:-)

> BTW: Do you think this error to be related to this late changes?

Not really. It sounds like binary/text mode is broken with this version of
cygwin. Many years ago, there was a version that had this problem. The library
ignored the 'b' in the fopen call, and opened all files in text mode, leading
to corruption when writing or reading 0x0a and 0x0d characters (which are
rather common, even in binary files).

> > There may also be problems with binary mounts noted in the FAQ.
>
> Where? I search http://www.cc65.org/faq.php for "binary" (2 matches, but
> no one which counts here), "cygwin", "mount", but did not find anything.

Sorry, I meant the Cygwin FAQ: http://www.cygwin.com/faq/. This is not a cc65
problem, so the cc65 faq doesn't handle it.

> I tried on another Win machine with a newer cygwin install:

Sounds even more like a problem with cygwin.

Regards


        Uz


-- 
Ullrich von Bassewitz                                  uz@musoftware.de
----------------------------------------------------------------------
To unsubscribe from the list send mail to majordomo@musoftware.de with
the string "unsubscribe cc65" in the body(!) of the mail.