From: Alan W. I. <ir...@be...> - 2002-01-20 03:02:43
|
On Sun, 20 Jan 2002, [iso-8859-1] Jo=E3o Cardoso wrote: > No, I concluded that the cvs version is more stable than my current > version. OK. > > | 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 ther= e are no // commentary issues this time. Could a C expert here deal with the remaining non-ANSI problems that Joao has found? Alan |