> Well, I now know why people say "Write once, test everywhere"
>
> If the code you write is not correct, sometimes it still produces
> what seems to be correct results on some platforms.
Well, there are few exceptions ;-)
Some are regarding platfome limitations
A complex proxy server application written here perfectly runs
under Windows NT and Linux JDK1.2 (green threads, grrrmbl). The
only exception: One thread under Windows NT consumes about 1
MB of memory each (think about 40+ clients), while using kernel
2.2.x under Linux, it does not.
HP/UX seems to be different, as they seem to violate the
specification regarding variable initialisation: A declared reference
is not definitely set to null, but to anything else.
> As some old Amiga engineers know, if the developer can not tell
> that the code was written incorrectly when they run it on their
> system, they assume it is correct code. (The Amiga examples are
Yes, I remember this MEMF_CHIP/MEMF_FAST problem.
It is the same habitude which now leads to the Y2K problem: "Hey,
who will ever use more than 2 decimals ?" converts into "Hey,
memory is memory", "Display resolution is always 1024x768
because I use it this way" and "My applet does not need more than
523x268 pixels and font 10 pt font size ".
Oliver
___________________________________________________
Oliver Fels | e-mail:
Neurotec Hochtechnologie GmbH | [EMAIL PROTECTED]
Team Manager JAVA-/IT-Security |
Friedrichshafen, Germany |
---------------------------------------------------
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
