: >: I like Windows95, it is just too hard to program for.
: >Get Unix. Easy to program for. Very easy to program for.
: >Great OS.
: <cough> <cough>
: What? Programming one variant of unix might be easy, but just you try
: to get your program to run on any other flavor. Do I need unistd.h?
: What's the directory type, dirent or direct, and which file do I include?
: Is function foo(3) available, and what are its parameters and return
: values? You're the FreeBSD missionary in this thread, what's that int variable
: that FreeBSD and NetBSD define in std[io|lib].h that all the programs out
: there use for error handling but don't expect it already defined? I want
: to say int errno, but I odn't think that's it.
Need I say `POSIX'?
Many programs get along fine by just #including stdlib.h, stdio.h, and
string.h, and unistd.h.
Only if you start doing funky directory/permission modification, user
parameter changes, etc. do you get stuck. fopen(), etc. is universal.
ncurses will run on just about any platform also.
Let me point out that no Mac program has that functionality.
: I like unix, but writing portable code is not exactly trivial. Otherwise
: we wouldn't need things like autoconf. ANd if you're not writing
: portable code, then why not?
Autoconf is a nice program. Makes programs portable easily.
: Or maybe you mean something like perl, python, or tcl, or whatever.
: OK, but I don't think you can really say that programming in perl, say,
: is really programming in Unix (unless you use stuff like getpwnam)
Well, what platform is tcl or perl programming for anyway? C is just about
the same for Unix as for any other character-based OS or system. GUIs tend
to unnecessarily complicate things.
--
John Goerzen, programmer and owner | Use #10 for your Win95 CD: it makes |
Communications Centre, Goessel, KS | an excellent cupholder. |