From: Maurice L. <mj...@ga...> - 2002-01-20 04:01:41
|
Alan W. Irwin writes: > > > > | Could somebody please volunteer to do a final comprehensive check > > | that the C code is ansi-compliant? This would take some release > > | burden off me. (I think I can recall how to check it, but if there > > | are warnings, I wouldn't know how to fix up the problems except for > > | the // commentary that screws up the Slowaris compiler.) > > > > I'm afraid that tk.c, around line 1229, uses some POSIX, non-ansi > > system calls, such as sigemptyset(), sigaddset() and sigprocmask(). > > It's only purpose is to "Don't kill plserver on a ^C if > > pls->server_nokill is set", and can safely be conditionaly compiled > > within a #ifndef __STRICT_ANSI__/#endif block. I don't commit this > > as I'm no ansi/posix expert, and it might be gcc (linux) specific. > > > > All other source files compiled OK, except for two warnings in > > plframe.c. It looks like that fdopen() and fileno() are not ansi > > compliant? > > Thanks very much for that comprehensive check. I am particularly glad there > are no // commentary issues this time. Could a C expert here deal with the > remaining non-ANSI problems that Joao has found? There's no problem with non-ANSI, but POSIX, function calls AFAIK. -- Maurice LeBrun mj...@ga... |