S#@>So port to C\C++....
S#@>Write in PURE C\C++
S#@>And Buy an OS/2 Compiler...
S#@>Now you can compile to any op system... Even Unix As long as you
S#@>write in PURE C .

Huh?  I am a C developer for DOS, Windows, and UNIX (developing on Sun
platforms, using both SunOS 4.1.4 and Solaris 2.4).  I work UNIX system
administration, and have to deal with cross-platform coding on a regular
basis.

I can guarantee you that programming in "pure" C is pretty useless.
If you think it's all that great, would you mind telling me whether the
string comparison call is 'strncasecmp' or 'strnicmp' or 'strnccmp'?
Should you #include <string.h> or <strings.h>?  Can you utilize fork()
calls?  Is malloc prototyped in <stdlib.h>, or <malloc.h>?  Can you
overwrite main's char **argv without causing a segmentation fault?
What is the semantics for <=?  (it changed with the ANSI standard).

FACT:  The ANSI standard for C doesn't define what's supposed to be in the
standard library, what it's going to be called, or where it's going to be
prototyped (there were guidelines, but they weren't a matter of compliance
for compiler implementers).  Pre-ANSI C (Kernigan and Richie C, or K&R C
for short) did not have specifically designated calls in the libraries,
either.  Sure, there are SOME standard things... but there are far more
things which AREN'T standard between platforms and even between compilers.
If you stick to those calls which are fairly standard, you usually do
okay... but there are a lot of things you can't do on all platforms (under
UNIX, for instance, you don't need to do write in assembler to get an
unbuffered stream of input.  Under DOS, that's not possible unless you use
a compiler-specific library option... and even then, you're not buffering
stdin, you're actually intercepting keyboard activity).

You generally need OPERATING SYSTEM DEPENDENT calls to do any useful work
at all, so you're talking about writing and porting, not writing perfectly
portable calls.

I hate to tell you this, but y'all just won't find a program that does any
hardware control that's really portable, unless your programmer goes to a
heckofa lot of work to write all the calls he needs and ignores most of the
standard library.  This tends to expand the size of the coding project to
unmanagable proportions... it's just not worth doing.

        -NR
---
 � OLX 2.1 TD � It's only a hobby ... only a hobby ... only a