Hi,
> > 3. as a result of (2) there is nothing a 100% java app can do to determine
> > the endianness of the platform it's being run on.
> If a Java app exchanges data with data from a non-Java program
> then it must face platform-specific endianness issues.
> Does a program fail to be 100% Pure Java if it exchanges
> data with a non-Java program? (I'm asking, I'm uncertain
> of the definition of "100% Pure Java". But, I'd expect
> the answer is "no".)
There have been a couple of comments on my sloppy use of the term "100%
Java". I believe my statement above remains correct, though.
From: http://java.sun.com/100percent/checklist.html
-----------------------------------------------------------------------
100% Pure JavaTM Defined:
In order to qualify for certification, products must conform to
the standards established by the 100% Pure Java Program, which
include:
1.No native methods.
2.Depend only on the Java Core APIs.
3.Follow any applicable API protocols.
4.No use of hardwired platform-specific constants.
-----------------------------------------------------------------------
Of course, you could write a java app that communicated with a native
server via sockets and determined endianness that way, but that would be
cheating. :)
Just adding to the noise,
dstn.
-----------------------------------------------
-- Dustin Lang, [EMAIL PROTECTED] --
(java developer, linux guy, green-haired freak)
Why Linux is so cool: /usr/include/string.h:190:
/* Sautee STRING briskly. */
extern char *strfry __P ((char *__string));
-----------------------------------------------
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
