Current restrictions


The NetRexx processor is rapidly evolving; features are being added almost daily to complete the implementation of the language. As of this version there are still a number of restrictions, listed below.

Please note that the presence of an item in this section is not a commitment to include that item or remove a restriction in some future update; NetRexx enhancements are dependent on on-going research, your feedback, and available resources. You should treat this list as a 'wish-list' (and please send in your wishes).

Implementation in progress

These items are work-in-progress:

Not yet implemented

The following planned language elements are not yet available (in a potential 'to-do' order):

Short-term restrictions

The following restrictions apply to the current NetRexx processor; they will be removed in due course:

Missing information and javac restrictions

At present, the Java class APIs do not expose full information on classes and their contents (if necessary, NetRexxC could read and parse the binary .class files for this information; this is under investigation). This leads to the following restrictions:

NetRexxC by default uses the javac compiler to generate bytecodes (class file). The following problem may occur in larger methods:

Long term restrictions

The following restrictions are due to the use of a translator, and would probably only be lifted if a direct-to-bytecodes NetRexx compiler were built.


[ previous section | contents]

From 'nrinst.doc', version 0.75.
Copyright(c) IBM Corporation, 1996. All rights reserved. ©