Mail Archives: djgpp/1998/06/29/08:18:34
> However, it's been my experience that the real portability problems are
> not in the language (which these try to catch), but in the library.
> E.g. some systems return different values from `sprintf', the flags for
> `access' are sometimes missing, etc, etc. This there currently isn't
> much you can do about automatically, but there's a project in the works
> to include some info on portability in the DJGPP docs.
Wouldn't that mean that the other system is not ANSI C?
tom
- Raw text -