Mail Archives: djgpp-workers/1998/02/12/05:03:05
On Wed, 11 Feb 1998, Nate Eldredge wrote:
> You're right. I shouldn't have implied Linux as being typical. I think it
> will be useful though, since its documentation is freely available and it's
> not too weird of a Unix-alike.
One ``problem'' with Linux is that it uses GNU libc, so expect it to
support any weird function out there.
> I wonder how should we coordinate all this. Do we swamp djgpp-workers with
> passing these lists back and forth? Is that a problem?
Somebody (you?) should coordinate the effort. Everybody else should
submit their contribution to that person. When the time comes to
review the results, if the file is too long, it can be uploaded to
DJ's and put into the v2/.alphas tree on SimTel.
> >(since all Unices are POSIX, aren't they?).
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> In a perfect world, yes. In real life, no. But I suspect as far as a C
> library goes, most Unices will be close.
Any Unix is a superset of POSIX. The extensions is where they differ.
> >I think you/we should decide how to format the information, and how much
> >information to give.
> Okay, here's an imaginary example of how an entry might look.
Here's another suggestion:
@subheading Portability
@multitable {Supported} {ANSI} {POSIX} {Unix} {MS-DOS/MS-Windows}
@item Supported? @tab no @tab yes @tab (1) @tab (2)
@end multitable
(1) SysV flavor doesn't frobnicate the foobar. BSD does. Many Unix
systems don't have the prototype declared anywhere (so it's best
to have an explicit prototype in the program).
(2) Known to be buggy in Borland. DOS compilers declare prototype
in @code{<io.h>}.
> Should this be worked on relative to the 2.02 alpha, or just to
> 2.01?
I suggest to use the latest v2.02 alphas as the baseline. It will
make it easier for DJ to apply the changes.
> If we do, can somebody do me a favor and give me a complete pointer
> to the alpha?
ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2/.alphas/980101/djlsr202.zip
- Raw text -