LSB & Posix Conflicts
An anonymous reader writes "The OpenGroup has published a detailed list of the conflicts between the Linux Standards Base and Posix ? that is accessible through their website. "
← Back to Stories (view on slashdot.org)
Perhaps we should just have a UNIX Standards BASE or USB.... oh wait..
Ahem. That's GNU/GNU/Linux, GNU/Posix, GNU/LSB, and GNU/Linux GNU/Distros. And the first word should be IMHGNU/O. So there. :-P
-- rms
SCO: "Too similar"
TOG: "Too different"
LSB: "Just right!"
Sheesh, evil *and* a jerk. -- Jade
Won't somebody think of the script kiddies!
099 2.1.2 gethostbyname [...]
102 2.1.3 getopt [...]
106 2.1.4 gets [...]
109 2.1.5 getservbyname [...]
112 2.1.6 getservent [...]
115 2.1.7 ioctl [...]
120 2.1.8 iswctype [...]
123 2.1.9 kill [...]
133 2.1.10 nice [...]
139 2.1.11 opterr, optind, optopt [...]
142 2.1.12 strptime
Pfff, we're saved. printf("Hello world\n") will still work on all platforms. Isn't it the standard portability test after all?
"A door is what a dog is perpetually on the wrong side of" - Ogden Nash
It seems that Posix has some updating to do.
> GNU has helpfully published a version of "Hello, World!" that uses autoconf
Why make things so complicated!
Sheesh, evil *and* a jerk. -- Jade
...because I only ever program in raw ANSI C89. You can't beat it for portability. There's only, like, 100 functions.
:-)
Of course, there's no hope for me writing something as simple as id or whoami, but still, I can just laugh when people bitch about standards.
Bash script for FP whores
(With apologies to the old "Dude" skit.)
"Learning is not compulsory... neither is survival."
--Dr.W.Edwards Deming
I'll admit it's a bit tedious, but it helps prevent gets overflows.
only on slashdot would a post about how to do something right get modded as flamebait...