RS>> But the compiled code works on all interpresters? So no linking is
RS>> used as C?
CC> Unlike proprietarty object code that's different for each c/c++
CC> compiler, java byte code is a standard and works on all inerpreters.
I take it that you didn't stop to think about what you were writing ? (-:
The object code generated by C/C++ compilers is *not* "different for each
[...] compiler". That's patently absurd. The object code used by the
compilers from (for example) Microsoft, Symantec, Watcom, Borland, MetaWare,
and IBM has to be the same across all of them, because the resulting programs
have to run on the same Intel x86 processors.
I'd also be careful about what you consider to be "standard". Until ISO, the
International Standards Organisation, gets a hand in the process, the Java
Virtual Machine is *exactly* as standard as is, say, Intel x86 machine code.
This is because the specifications for the Java Virtual Machine are still
under the control of one company, just like the specifications for the x86
instruction set are under the control of Intel corporation. Knowing how the
standards process works, I don't see this changing for at least another two
years.
¯ JdeBP ®
--- FleetStreet 1.19 NR
---------------
* Origin: JdeBP's point, using Squish (2:440/4.3)
|