ILU Reference Manual

(1)

If the Internet Engineering Task Force working on Uniform Resource Identifiers and Locators come up with something useful, we will probably switch to those forms for object ID's and string binding handles.

(2)

We might forbid two consecutive hyphens or add other restrictions.

(3)

We may change this.

(4)

Same integer in all protocols? Yep -- for now.

(5)

See section The ILU Common Lisp Portable DEFSYSTEM Module, for a description of the PDEFSYS package.

(6)

This causes problems; the ISL names "FooBar" and "foo-bar" map to the same Common Lisp name. Something will have to change.

(7)

This conflicts with the tagged-union approach of CORBA, and has to be changed to support ILU's support for CORBA.

(8)

This class also contains functions which are only used by generated code, and which the programmer will never use

(9)

The Common Object Request Broker: Architecture and Specification, OMG document number 93.12.43, revision 1.2, Draft 29 December 1993

(10)

We will probably move the type field into the SBH in the near future.

(11)

This should be done with a generated macro, and will be, in the next release.

(12)

At PARC we are using 1.2, as it provides better identifier name safety.

(13)

IDL is defined in: The Common Object Request Broker: Architecture and Specification, OMG Document Number 91.12.1, Revision 1.1

(14)

See the file `src/stubbers/idl2isl/Sun-parser/docs/COPYRIGHT' in the ILU distribution.