* annoying include incompatibilities
@ 2000-05-29 14:12 towo
0 siblings, 0 replies; only message in thread
From: towo @ 2000-05-29 14:12 UTC (permalink / raw)
To: cygwin
I installed a complete new Cygwin 1.1.1 now, and uninstalled B20.
As my application did not work anymore it seemed I had to recompile it.
First, it did not compile anymore.
There was a recent mail here apparently related to the problem
about sys_errno and sys_errlist. Obviously someone thought it would be
fun just to rename these two and waste thousands of developers' time
world-wide (who have to adapt their software after finding out what's
going on) by introducing incompatibilities with long-established Unix
standards. Or is there any real reason for this game?
Now, it does compile but only with a warning about this completely
superfluous "const" stuff in the new errno definition. I was annoyed
already when the SuSe Linux distribution had introduced some similar
nonsense (and some other nonsense where #include <linux/termios.h> is
now needed instead of just <termios.h>).
All this voguish "assumedly-modern C" junk only increases portability
problems and wastes developers' time. It's nothing but a nuisance.
Could people who play around with definitions in an incompatible way
please at least provide information on how to detect their patch with
#ifdef's? I have no idea how to handle the "const" crap in a general way.
Kind regards,
Thomas Wolff
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2000-05-29 14:12 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-05-29 14:12 annoying include incompatibilities towo
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).