NetRexx Changes

NetRexx Change History

NetRexx 1.1xx

This release is the reference implementation for NetRexx 1.1xx, and requires Java 1.1 to run. NetRexx 1.1xx releases are a superset of NetRexx 1.00, as published in The NetRexx Language. New features in NetRexx 1.1xx are documented in the NetRexx Supplement.

Updates:

1.113
[3 Aug 1997]

Multiple .java files are compiled using a single call to javac, giving improved performance and interdependency resolution.
Individual methods may be designated as binary, using the binary keyword.
Numerous 'cosmetic' improvements in error messages, formatting, etc.

1.104
[22 Jul 1997]

Whole numbers may now be expressed in a hexadecimal or binary notation, for example: 0xbeef 2x81 8b10101010 - see the Supplement for details.
Conversions from String to Rexx (etc.) now 'pass through' nulls, rather than raising NullPointerException.
options symbols may be used to include debugging information (a symbol table) in the generated .class files.
Numerous 'cosmetic' improvements in error messages, formatting, etc.

1.103
[3 Jul 1997]

A new modifier, adapter, for classes has been introduced. This makes it easy to use Java 1.1 events, without the complexity and extra nesting of Java Inner Classes. Please see the Supplement for details, and the new Scribble sample for a simple example.
Compressed Zip files as produced by the Java 1.1 jar utility ('jar files') can now be used for class file collections. The current NetRexxC.zip file is such a file.
The NetRexx string class, netrexx.lang.Rexx, is now serializable.
The compiler now uses the Java 1.1 Writer and Reader classes for reading and writing text files; this means that the text code page in use on your machine will be automatically translated to and from Unicode for use by the compiler.
Associated with the previous change, options utf8 must now be consistent with the options passed to the compiler (see the Supplement for details).
The NetRexxC.properties (error messages) file is now included as a resource in the NetRexxC.zip file. The copy in the \lib directory is no longer needed, nor is the NETREXX_HOME environment variable (if you needed to use that before).
The Pinger and Spectrum sample applications have been updated to use the Java 1.1 event model; Pinger has also had some other minor improvements.
Performance improvements reduce start-up time when compiling with a long CLASSPATH or with class directories with large numbers of files.

NetRexx 1.0x

This release is the reference implementation for NetRexx 1.00, as published in The NetRexx Language, and later updates. NetRexx 1.0x updates will run on Java 1.0.1 or any later releases, though certain new features may require a Java 1.1 compiler to compile the generated Java code.

A change list for earlier releases of NetRexx is also available.

Updates:

1.02
[25 Jun 1997]

You can now add the shared keyword to the method or properties instructions to indicate that the method or a following property has shared access (that is, is accessible to other classes in the same package, but not to other classes). This corresponds to the Java 1.1 'default access' visibility. Please see the NetRexx Supplement for details.
The new sourceline special name may be used to return the line number of the current clause in the program. Please see the NetRexx Supplement for details.
Array initializers have ben added. These allow arrays to be created and assigned an initial value, for example: x=['one','two','three'] Note that Java 1.1 is needed to use this enhancement. Please see the NetRexx Supplement for details.
The property and method access rules have been enforced according to the current Java specification, along with enhanced error messages when the rules are infringed.

1.01
[15 Jun 1997]

The NetRexx Supplement has been added. This documents language enhancements and the netrexx.lang package.
NetRexxC now displays a warning when it encounters any deprecated (out-of-date or no longer recommended) class, method, or property for the first time in a program.
Note that under Java 1.1, the javac compiler always displays at least one message if any deprecated fields or classes are encountered. The invitation to 'Recompile with "-deprecation" for details' can be ignored.
You can now add the deprecated keyword to the class, method, or properties instructions to indicate that the following class, method, or properties are deprecated. You have to run with a Java 1.1 compiler for this to be reflected in the .class file.
Methods and properties with the same name are now permitted (and can be accessed).
An import of one of the standard packages (for example, java.io) no longer causes the classpath to be searched. This makes redundant standard imports much faster.

1.00
[24 May 1997]

Cosmetic changes:

Methods listed during compilation now have their argument types listed (if any)
Methods generated from Indirect Properties are now listed.

The installation instructions now include instructions for using NetRexx with Visual J++.
A reference to java.awt.image.ImageObserver treated java.awt.image as a class reference rather than as a package name; it will now correctly refer to the ImageObserver class.

[6 May 1997]

Multiple file concurrent compilation: when two or more programs are specifed on the NetRexxC command, they are all compiled with the same class context: that is, they can 'see' the classes, properties, and methods of the other programs being compiled, much as though they were all in one file. This allows mutually interdependent programs and classes to be compiled in a single operation, while maintaining their independence (the programs may have different options, import, and package instructions).
Compiling programs together in this way also gives substantial performance improvements, as the classes for NetRexxC and the javac compiler are only loaded once for all the files being compiled. See Using the NetRexx compiler in the NetRexx User's Guide for full details.
The warning 'Method argument not used' will now only be given if the strictargs option is specified.
The '.crossref' and '.java.keep' files resulting from a compilation now are placed in the same directory as the source file (instead of the current directory). The multiple compilation support also requires that the source directory be writeable.
import of a package (with no trailing period) was not accepted by the compiler; this should now work correctly.

[15 Apr 1997]

Preliminary, experimental, support for JavaBeans is now available in the NetRexxC compiler. It is described in the NetRexx Supplement.
Checking has been added for the use of Java reserved words as externally visible names (such properties, method, and class names cannot be accessed by people writing in the Java language).
The translator phase of the compiler has numerous performance improvements, and now runs 35% faster than the first (January) 1.00 release.
Forward references from property initialization expressions to methods in the current class are now permitted, providing they are not circular.
Several improvements have been made to error and progress messages.

[13 Mar 1997]

The source and documentation for the Tablet (navigation tabs) applet have been added to the package.
Forward references involving default constructors now work correctly.
The .equals method was not being used for '=' and '\=' comparisons of subclassed objects.
options nodecimal may be used to report the use of decimal arithmetic as an error, for performance-critical applications.

[18 Feb 1997]

Minor improvements to the compiler for error messages, localization, and Java 1.1.
The Say instruction can now handle all expressions that evaluate to null.

[6 Feb 1997]

LOOP OVER did not correctly snapshot indexed strings with 'hidden' elements.
Some unused method arguments were not being reported as unused.
Minor improvements to error messages, progress messages, and code generation.

[3 Jan 1997]

Minor cosmetic and performance improvements over 0.90.
NetRexxC.bat and nrc.bat have been added to the NetRexx package.

This page was created on 3 Aug 1997; it can be found from http://www2.hursley.ibm.com/netrexx/

Updates:
1.113 [3 Aug 1997]	Multiple .java files are compiled using a single call to javac, giving improved performance and interdependency resolution. Individual methods may be designated as binary, using the binary keyword. Numerous 'cosmetic' improvements in error messages, formatting, etc.
1.104 [22 Jul 1997]	Whole numbers may now be expressed in a hexadecimal or binary notation, for example: `0xbeef 2x81 8b10101010` - see the Supplement for details. Conversions from `String` to `Rexx` (etc.) now 'pass through' nulls, rather than raising `NullPointerException`. options symbols may be used to include debugging information (a symbol table) in the generated `.class` files. Numerous 'cosmetic' improvements in error messages, formatting, etc.
1.103 [3 Jul 1997]	A new modifier, adapter, for classes has been introduced. This makes it easy to use Java 1.1 events, without the complexity and extra nesting of Java Inner Classes. Please see the Supplement for details, and the new Scribble sample for a simple example. Compressed Zip files as produced by the Java 1.1 `jar` utility ('jar files') can now be used for class file collections. The current NetRexxC.zip file is such a file. The NetRexx string class, `netrexx.lang.Rexx`, is now serializable. The compiler now uses the Java 1.1 Writer and Reader classes for reading and writing text files; this means that the text code page in use on your machine will be automatically translated to and from Unicode for use by the compiler. Associated with the previous change, options utf8 must now be consistent with the options passed to the compiler (see the Supplement for details). The `NetRexxC.properties` (error messages) file is now included as a resource in the NetRexxC.zip file. The copy in the \lib directory is no longer needed, nor is the NETREXX_HOME environment variable (if you needed to use that before). The Pinger and Spectrum sample applications have been updated to use the Java 1.1 event model; Pinger has also had some other minor improvements. Performance improvements reduce start-up time when compiling with a long CLASSPATH or with class directories with large numbers of files.

Updates:
1.02 [25 Jun 1997]	You can now add the shared keyword to the method or properties instructions to indicate that the method or a following property has shared access (that is, is accessible to other classes in the same package, but not to other classes). This corresponds to the Java 1.1 'default access' visibility. Please see the NetRexx Supplement for details. The new sourceline special name may be used to return the line number of the current clause in the program. Please see the NetRexx Supplement for details. Array initializers have ben added. These allow arrays to be created and assigned an initial value, for example: `x=['one','two','three']` Note that Java 1.1 is needed to use this enhancement. Please see the NetRexx Supplement for details. The property and method access rules have been enforced according to the current Java specification, along with enhanced error messages when the rules are infringed.
1.01 [15 Jun 1997]	The NetRexx Supplement has been added. This documents language enhancements and the `netrexx.lang` package. NetRexxC now displays a warning when it encounters any deprecated (out-of-date or no longer recommended) class, method, or property for the first time in a program. Note that under Java 1.1, the javac compiler always displays at least one message if any deprecated fields or classes are encountered. The invitation to 'Recompile with "-deprecation" for details' can be ignored. You can now add the deprecated keyword to the class, method, or properties instructions to indicate that the following class, method, or properties are deprecated. You have to run with a Java 1.1 compiler for this to be reflected in the `.class` file. Methods and properties with the same name are now permitted (and can be accessed). An import of one of the standard packages (for example, `java.io`) no longer causes the classpath to be searched. This makes redundant standard imports much faster.
1.00 [24 May 1997]	Cosmetic changes: Methods listed during compilation now have their argument types listed (if any) Methods generated from Indirect Properties are now listed. The installation instructions now include instructions for using NetRexx with Visual J++. A reference to java.awt.image.ImageObserver treated java.awt.image as a class reference rather than as a package name; it will now correctly refer to the ImageObserver class.
[6 May 1997]	Multiple file concurrent compilation: when two or more programs are specifed on the NetRexxC command, they are all compiled with the same class context: that is, they can 'see' the classes, properties, and methods of the other programs being compiled, much as though they were all in one file. This allows mutually interdependent programs and classes to be compiled in a single operation, while maintaining their independence (the programs may have different options, import, and package instructions). Compiling programs together in this way also gives substantial performance improvements, as the classes for NetRexxC and the javac compiler are only loaded once for all the files being compiled. See Using the NetRexx compiler in the NetRexx User's Guide for full details. The warning 'Method argument not used' will now only be given if the strictargs option is specified. The '.crossref' and '.java.keep' files resulting from a compilation now are placed in the same directory as the source file (instead of the current directory). The multiple compilation support also requires that the source directory be writeable. import of a package (with no trailing period) was not accepted by the compiler; this should now work correctly.
[15 Apr 1997]	Preliminary, experimental, support for JavaBeans is now available in the NetRexxC compiler. It is described in the NetRexx Supplement. Checking has been added for the use of Java reserved words as externally visible names (such properties, method, and class names cannot be accessed by people writing in the Java language). The translator phase of the compiler has numerous performance improvements, and now runs 35% faster than the first (January) 1.00 release. Forward references from property initialization expressions to methods in the current class are now permitted, providing they are not circular. Several improvements have been made to error and progress messages.
[13 Mar 1997]	The source and documentation for the Tablet (navigation tabs) applet have been added to the package. Forward references involving default constructors now work correctly. The `.equals` method was not being used for '=' and '\=' comparisons of subclassed objects. options nodecimal may be used to report the use of decimal arithmetic as an error, for performance-critical applications.
[18 Feb 1997]	Minor improvements to the compiler for error messages, localization, and Java 1.1. The Say instruction can now handle all expressions that evaluate to `null`.
[6 Feb 1997]	LOOP OVER did not correctly snapshot indexed strings with 'hidden' elements. Some unused method arguments were not being reported as unused. Minor improvements to error messages, progress messages, and code generation.
[3 Jan 1997]	Minor cosmetic and performance improvements over 0.90. NetRexxC.bat and nrc.bat have been added to the NetRexx package.