> You'll have to implement it yourself. (Ouch!)

Signature
Darryl L. Pierce <mcpierce@gmail.com>
Homepage: http://mcpierce.multiply.com/
"Bury me next to my wife. Nothing too fancy..." - Ulysses S. Grant
I'm going to combine some of Darryl L. Pierce's replies into this one big
message.
"Darryl L. Pierce" <mcpierce@gmail.com> wrote in message
news:ODr5f.37167$Lp.33159@bignews5.bellsouth.net...
>> did you try isSpace() instead of isWhitespace() ? If the former
>> works, you may want to update your class library. Also, AFAIK the J2ME
[quoted text clipped - 3 lines]
> However it does *not* provide all APIs from JavaSE. The right thing would
> be to check the MIDP APIs, which excludes the isWhiteSpace() method...
You are right about the MIDP having the Character class. I had
downloaded the MIDP API and looked at the "All Classes" list on the left
frame, noticed that "Character" did not appear there, and so assumed that
the Character class was not present in the library. However, if I click on
the package "java.lang", Character does show up, but not as a link (implying
that it's not documented, I guess).
>> You'll have to implement it yourself. (Ouch!)
>
> Which you can't do since both licensing and implementations disallow
> including java.lang.* classes in your code.
I'm not sure I understand what you're said here, but my understanding is
that the OP wants the functionality of the isWhitespace() method, and the
MIDP class library doesn't provide it, so I'm saying the OP should implement
that functionality himself, e.g.:
public class MyUtilityClass {
public static boolean naiveImplementationOfIsWhitespace(char c) {
return c = ' ';
}
}
I doubt that something like the above will put the OP in any legal
trouble.
- Oliver
Roedy Green - 20 Oct 2005 01:51 GMT
> I doubt that something like the above will put the OP in any legal
>trouble.
I think the legal trouble might come cannibalising the J2SE
Chararacter class and sticking it in MIDP.

Signature
Canadian Mind Products, Roedy Green.
http://mindprod.com Again taking new Java programming contracts.
Darryl L. Pierce - 20 Oct 2005 12:45 GMT
>>> You'll have to implement it yourself. (Ouch!)
>>
>>Which you can't do since both licensing and implementations disallow
>>including java.lang.* classes in your code.
>
> I'm not sure I understand what you're said here,
My statement is clear: no classes that are packaged as java[x].* are
allowed to be included in a MIDlet suite. This restriction exists both
as a licensing element (read the license for the WTK, the MIDP RI, etc.)
and as an implementation detail (if you include such a class then all
MIDP implementations will fail the suite during verification).

Signature
Darryl L. Pierce <mcpierce@gmail.com>
Homepage: http://mcpierce.multiply.com/
"Bury me next to my wife. Nothing too fancy..." - Ulysses S. Grant