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. "

Comments

UNIX standards base

[Anonymous Coward]

Perhaps we should just have a UNIX Standards BASE or USB.... oh wait..

Re:UNIX standards base

[Surak]

Well, there is the older standard, POSIX Standards/2 (or PS/2)...

Re:POSIX LSB

[Anonymous Coward]

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

Goldilinux and the three bears...

[Black Parrot]

SCO: "Too similar"
TOG: "Too different"
LSB: "Just right!"

gets()

[Genghis Troll]

107 The LSB has deprecated the gets() function, whereas it is a first
108 class function in ISO/IEC 9945 and ISO/IEC 9899.

Won't somebody think of the script kiddies!

Re:gets()

[Surak]

No programmer in their right mind uses the I/O POSIX functions without checking the user input. Too bad there are still very common buffer overflows, format strings and heap overflows found in (more or less major) projects.

I do, but then again, I'm working on a project that requires Windows compatibility. ;)

Affected C functions

[Rosco P. Coltrane]

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?

Re:Affected C functions

[AJWM]

Good God, it's 380KB zipped.

Yeah, but check the description page to see why:

"Yes, this really is the classic program that prints "Hello, world!" when you run it. Unlike the elementary version often presented in books like K&R, GNU hello processes its argument list to modify its behavior, supports internationalization, and includes a mail reader."

(emphasis added).

Who was it that said something about every program tending to add features until it includes a mail reader?

Oops

[KillerHamster]

We had better fix this. I'll go ask SCO what to do.

Well

[Anonymous Coward]

It seems that Posix has some updating to do.

Standards

[mark_slashdot]

"The nice thing about standards is that you have so many to choose from" -- Andrew S. Tanenbaum

My hello program.

[Black Parrot]

> GNU has helpfully published a version of "Hello, World!" that uses autoconf

Why make things so complicated!

# Makefile for "Hello World" program.
#
hello:
@echo "Hello, World!"

Re: Why does the Open Group care?

[Black Parrot]

> What part of GNU's not Unix don't they understand?

Maybe they haven't finished expanding the acronym yet.

It's times like this I feel smug...

[James A. A. Joyce]

...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. :-)

Re:WRONG! POSIX does some really dumb things!!

[Anonymous Coward]

(psst... | is or, & is and )

Re: Why does the Open Group care?

[EvilTwinSkippy]

Yes, but the question is subtler. Does GNU mean:

• GNU Not Unix! (Take that)
• GNU Not Unix? (Say What?)
• GNU Not Unix!? (Now you tell me.)
• GNU Not Unix. (We came, we saw, we implemented.)

(With apologies to the old "Dude" skit.)

what I do

[martin-boundary]

Right on! What I usually do when I use gets is this:

char buf[10];
char dummy[10];

fgets(dummy, 10, stdin);
n = strlen(dummy);
ungetc('\n', stdin);
for(i = n - 1; i >= 0; i++) {
ungetc(dummy[i], stdin);
}

gets(buf);

I'll admit it's a bit tedious, but it helps prevent gets overflows.

Re:That is the STUPIDEST solution I have ever seen

[dakoda]

only on slashdot would a post about how to do something right get modded as flamebait...