BL> I didn't know that. The machine code has to be the same, so to
 BL> me it seemed feasible.

 DB> For multiple operating systems on the same hardware platform,
 DB> the "machine code" (more or less) *is* the same - what changes
 DB> is calling patterns (how parameters are passed between
 DB> functions), file formats (of the executables and libraries),
 DB> and of course the links to the libraries themselves. 

  I'm surprised that they haven't standardised even that.

 DB> It is in fact possible to compile code for a completely
 DB> different platform (say, build a Sun SPARC application on an
 DB> Intel 486) as long as you use software that supports this (like
 DB> GCC under UNIX does), and have the necessary libraries in
 DB> place. 

  Ahh... thank you, David. That's more-or-less what made sense.

 BL> I'm trying to *learn* something.

 DB> Whatever happened to reinventing an even better wheel, without
 DB> the mental inhibitions and limitations of the original
 DB> inventor(s)? ;-) 

  That's all part of it. Education is a very tricky business. If you
let yourself become overwhwelmed by too much knowledge you create a
parrot who can't think, but if you have gaps in the knowledge you
create a fool who never knows there are bits missing. Personally, I
lean more towards the fool. You can always fill in gaps, as long as
you are never foolish enough to think you know it all. Parrots on the
other hand, know it all... and that's where it ends.

  In my experience, the most important thing is to think, originally.
That's where the money is, and it's more fun anyway.

Regards,
Bob


    
___ Blue Wave/QWK v2.12
@EOT:

---