Artifact Content

Artifact eae116c9058f5cfb9be42505a3c3e8a093262bee:


Compatibility

SquirrelJME aims to be compatible with most programs however there are situations and rare edge cases where there will be no compatibility. This is to make the implementation easier.

Flushable Interface

The interface Flushable does not exist in Java ME and as such it does not exist in SquirrelJME.

LCDUI Display Input

Only the first display (index zero) supports input events such as keyboard, buttons, mice, and touchscreen. Any secondary displays which are attached will not have events handled for them at all. This is to make it easier to implement.

Limited Network Interface Support

The Generic Connection Framework (GCF) has API to provide access to various system interfaces, WiFi devices, 3GPP/CDMA (Mobile data), and dial-up connections. Since supporting all of these are complicated, support for these across systems will be limited to an as needed basis.

Reader's lock Is null

Since SquirrelJME uses a reference counted garbage collector the Reader's lock object in the default constructor is set to null instead of this. This is so that readers do not remain in memory unable to be freed because objects still refer to them and such.

SUPER Is Always Set

In all clases the SUPER flag is assumed to be set, this flag just modifies the behavior of invokespecial. When it is not set then that instruction can invoke nearly every method directly (it was called before invokenonvirtual). However, the Java compiler since Java 1.1 always set the flag for classes it compiled. Since CLDC 1.0 was released well after Java 2 was and is defined as a Java 2 virtual machine all code written for J2ME should have classes where this flag is set. As such instead of supporting the logic to handle cases where it is not set, the flag will just be ignored and assumed to be set.

Supported Encodings

Only the following character encodings are supported:

Note that UTF codepoints above U+FFFF are not fully supported and are not available in Java ME. Surrogate pairs in UTF-16 will be encoded in UTF-8 as six bytes. Additionally when decoding, if a sequence that is above U+FFFF is read then it will decode to the replacement character. This may cause a loss of or mutation of data when processing files.

See: