@setfilename ilu-installation.info
@settitle ILU Installation Instructions, release RELEASE_NUMBER
@ifclear largerdoc
@titlepage
@title ILU Installation Instructions, release RELEASE_NUMBER
@author Bill Janssen @code{<janssen@@parc.xerox.com>}
@sp
(typeset @today{})
@sp
Copyright @copyright{} 1994, 1995 Xerox Corporation@*
All Rights Reserved.
@end titlepage
@end ifclear

This document describes the installation of version RELEASE_NUMBER of the
Inter-Language Unification (@system{ILU}) system.

@emph{If you succeed in installing @system{ILU} on a particular platform,
we'd appreciate it if you could send a note to @code{ilu-core@@parc.xerox.com}
telling us (1) what operating system you succeeded with, and what version
of that OS, (2) which versions of what compilers you used, and (3) which
version of @system{ILU} you used.  We're accumulating
a list of operating systems and compilers that work with @system{ILU}.  If you
had to make any changes to make it work on your system, please send them
along, and we'll incorporate them into the next release.}

@section Installing on a UNIX System

@subsection Prerequisites

You will need an @language{ANSI C} compiler to build and install
@system{ILU}, along with an @language{ANSI C}-compliant @file{libc.a}.
Note that @system{GNU} @program{gcc} doesn't always work as an @language{ANSI C} compiler.
The simple test we use to qualify a compiler is whether it can compile and link
the following program without warnings or errors:

@codeexample
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <limits.h>
int main(int ac, char **av) @{
 int i = INT_MAX;
 char *p = (char *) malloc(1048);
 memmove(p, *av, strlen(*av)+1);
 printf("%s %d\n", p, i);
 return 0;
@}
@end codeexample

@system{ILU} requires the @program{imake} program from the MIT X Consortium release
of the @system{X Window System}, version 4 or later.  This is available via FTP
from the ftp servers @code{ftp.x.org} on the East Coast, or @code{gatekeeper.dec.com}
on the West Coast.  You can also get it from@br
@code{ftp://ftp.parc.xerox.com/pub/ilu/imake/imake.tar.gz}.

@system{ILU} normally provides support for a number of languages, currently @language{ANSI C}, @language{C++},
@language{Modula-3}, @language{Python}, and @language{Common Lisp} (Franz Allegro 4.2, and Harlequin LispWorks), but the 2.0alpha release only contains support for @language{ANSI C}, @language{C++}, and
@language{Python}.
@itemize @bullet
@item
If you wish to build the support for @language{ANSI C}, you will need a @language{C}
compiler, and an @language{ANSI C}-compliant libc.  But you already need that to build @system{ILU}.
@item
If you wish to build the support for @language{C++}, you will need a @language{C++}
compiler that conforms to version 2.0 of the C++ specification.  @system{ILU} does not use
either @language{C++} templates or exceptions, as these are too spottily implemented
to be relied on.  The @system{GNU} @language{C}/@language{C++} compiler @program{g++} seems
to work well with @system{ILU}.  It has also been tested with Lucid's Energize @program{lcc} compiler,
CenterLine's @program{CC} compiler, and Sun's @program{CC} compiler.
@item
If you wish to build support for @language{Modula-3}, you will need to wait for the 2.0beta
release.
@item
If you wish to build the support for @language{Common Lisp}, you will need to wait for
the 2.0beta release.
@item
If you with to build support for @language{Python}, you will need the @language{Python} 1.2 (or later)
release, available via FTP from @file{ftp://ftp.cwi.nl/pub/python/}.  When installing @language{Python} on your system,
be sure to do a "make inclinstall", so that the include files are installed for @system{ILU}'s use.
It's also advisable to do "make libainstall", if you wish to try the `multiple languages in the same
address space' example.
@end itemize

@subsection For the Impatient

You can try just unpacking it, and typing

@transcript
% @userinput{make}
@end transcript

at the top of the source tree.  A minimal configuration using defaults will be built,
sufficient for testing.

@subsection Real Configuration

Begin by creating two directories:  one, @metavar{ILUHOME}, to install the @system{ILU} in,
and the other, @metavar{ILUSRC}, to unpack the sources in, and build the system in.
It is often convenient if @metavar{ILUSRC} is a sub-directory of @metavar{ILUHOME}, but
it is not necessary.  At PARC, we use @file{/import/ilu} for @metavar{ILUHOME}, and @file{/import/ilu/src}
for @metavar{ILUSRC}.

Copy the compressed tar file @file{ilu-RELEASE_NUMBER.tar.Z} or @file{ilu-RELEASE_NUMBER.tar.gz} to
@metavar{ILUSRC}.  Uncompress it if necessary with
the @program{uncompress} or @program{gunzip} program:

@transcript
% @userinput{uncompress ilu-RELEASE_NUMBER.tar.Z}
@end transcript

or

@transcript
% @userinput{gunzip ilu-RELEASE_NUMBER.tar.gz}
@end transcript

Then unpack the tar file:

@transcript
% @userinput{tar xf ilu-RELEASE_NUMBER.tar}
@end transcript

@system{ILU} uses the GNU @system{autoconf} system to configure the
release, before building.  The very simplest way to configure your
system is type type 

@transcript
% @userinput{./configure}
@end transcript

@noindent
at the top of the source tree.

What will happen is that @program{@metavar{ILUSRC}/imake/configure} will go out and look along
the value of your PATH environment variable for various executable
programs.  If it finds @program{cc}, it will assume that you want to build
@language{ANSI C} support for @system{ILU}.  If it finds @program{m3}, it will assume
that you want to build @language{Modula-3} support for @system{ILU}.  If it
finds @program{cl} or @program{franz}, it will assume that you want to build
@language{Lisp} support for @system{ILU}.  If it finds @program{python}, it will
assume that you want to build @language{Python} support for
@system{ILU}.  If it finds @program{CC} or @program{cxx} or @program{c++}, it will assume that you want to build
@language{C++} support for @system{ILU}.  It will also assume that the
first executable with an appropriate name is the one you wish to use for
compiling programs in that language.  By default, it will assume that you
wish to include support only for using @protocol{ONC RPC} over @transport{TCP/IP}.
By default, it will assume that you do not wish to provide support for @language{OMG IDL}.

@program{imake} must be on your path, or in @file{/usr/bin/X11/}, for the build to work properly.

@subsubsection @program{configure} Options

The program @program{configure} can be invoked with a number of options, to customize
the build for your site.  It actually supports more options than shown here, but these
are the only options that will work at this point in the release process.

@itemize @bullet
@item
@var{--with-destdir=PATH} -- this should be the name of the directory you would like
the files installed into, in the @userinput{make Install} step.  The default
is @file{/usr/local/ilu}, which may be OK for your system.
@item
@var{--with-iluhome=PATH} -- this should be the name of the directory
users will expect @system{ILU} to be installed under, the value of @metavar{ILUHOME}.  The two options
@var{--with-destdir} and @var{--with-iluhome} are provided separately because a directory may have
two different names that are used to access it in different ways.  At PARC, for instance,
installation directories are often write-protected if named with their ordinary names,
and a special name has to be given to enable writing in that directory.  If your site
does not have this type of restriction, the switches for @var{--with-destdir} and @var{--with-iluhome}
should probably have the same values.  Note that the default is @file{/usr/local/ilu}, which
may be OK for your system.
@item
@var{--prefix=PATH} -- if specified, this becomes the default for @metavar{ILUHOME} and @metavar{DESTDIR},
if they are not specified explicitly.
@item
@var{--with-binding-dir=PATH} -- a world-writable directory in a file system,
for supporting the "simple binding" service described in Chapter 1.
@item
@var{--enable-sunrpc-protocol} -- compiles in support for using @protocol{ONC RPC} across address spaces.  (Enabled by default.)
@item
@var{--enable-courier-protocol} -- compiles in support for using @protocol{XNS Courier RPC} across address spaces.  (Disabled by default)
@item
@var{--enable-corba-iiop} -- compiles in support for using the @system{CORBA} @protocol{Internet Inter-Orb Protocol} across address spaces.  (Disabled by default)
@item
@var{--enable-tcp-transport} -- compiles in support for using @transport{TCP/IP} to transport messages.  (Enabled by default.)
@item
@var{--enable-udp-transport} -- compiles in support for using @transport{UDP/IP} to transport messages.  (Disabled by default)
@item
@var{--enable-omg-idl-support} -- builds the support for using @language{OMG IDL} with @system{ILU}.  You will need to have a @language{C++} compiler (CFRONT 3.0 or later) on your path.  @program{g++} seems to work fine.  (Disabled by default)
@item
@var{--enable-xview-support} -- builds the libraries to interface the @system{XView} GUI library to the @system{ILU} main loop.  (Disabled by default)
@item
@var{--enable-xt-support} -- builds the libraries to interface @system{Xt}-based GUI libraries to the @system{ILU} main loop.  (Disabled by default)
@item
@var{--enable-tk-support} -- builds the libraries to interface @system{Tk}-based GUI libraries to the @system{ILU} main loop.  (Disabled by default)
@item
@var{--disable-c-support} -- disables @language{C} support.  (Enabled by default.)
@item
@var{--enable-cplusplus-support@{=@metavar{PROG}@}} -- enables @language{C++} support.  If @metavar{PROG} is specified, treats @metavar{PROG} as the command to use for @language{C++} compilation.  Default is to enable
@language{C++} support iff the environment variable @metavar{CXX} is defined,
in which case @metavar{CXX} should be the compilation command.
@item
@var{--enable-python-support@{=@metavar{PYTHON-HOME}@}} -- enables @language{Python} support.  If @metavar{PYTHON-HOME} is specified, treats @metavar{PYTHON-HOME} as the directory in which the @language{Python} system is installed.  Default is enabled.
@end itemize

Features that are enabled by @var{--enable-FEATURE} may also be explicitly disabled with @var{--disable-FEATURE}.

The particular @language{ANSI C} compiler to use may be specified by setting the environment variable @var{CC} to the full path name of the C compilation command before running @program{configure}.  Similarly, the particular C++ compiler to use may be specified by setting the environment variable @var{CXX} to the full path name of the C++ compilation command to use.

@subsection Building

Now that you have configured the release, do the following to build the system.  Note
that the capitalization of the arguments to @program{make} is important.

@enumerate
@item
Set your working directory to @metavar{ILUSRC}:
@transcript
% @userinput{cd @metavar{ILUSRC}}
@end transcript

@item
Build the system with the command:
@transcript
% @userinput{make}
@end transcript

@item
You can then try a simple test with:
@transcript
% @userinput{cd @metavar{ILUSRC}/examples/test1}
% @userinput{make test}
../../stubbers/c/c-stubber  Test1.isl
header file for interface Test1 to ./Test1.h...
common code for interface Test1 to ./Test1-common.c...
code for surrogate stubs of interface Test1 to ./Test1-surrogate.c...
code for true stubs of interface Test1 to ./Test1-true.c...
../../stubbers/c/c-stubber  Test2.isl
header file for interface Test2 to ./Test2.h...
common code for interface Test2 to ./Test2-common.c...
code for surrogate stubs of interface Test2 to ./Test2-surrogate.c...
code for true stubs of interface Test2 to ./Test2-true.c...
../../stubbers/c/c-stubber  Test3.isl
header file for interface Test3 to ./Test3.h...
common code for interface Test3 to ./Test3-common.c...
code for surrogate stubs of interface Test3 to ./Test3-surrogate.c...
code for true stubs of interface Test3 to ./Test3-true.c...
rm -f clnt.o
cc -c  -g -I. -I../../runtime/c -I../../runtime/kernel clnt.c
rm -f Test1-surrogate.o
cc -c  -g -I. -I../../runtime/c -I../../runtime/kernel Test1-surrogate.c
rm -f Test1-common.o
cc -c  -g -I. -I../../runtime/c -I../../runtime/kernel Test1-common.c
rm -f Test2-surrogate.o
cc -c  -g -I. -I../../runtime/c -I../../runtime/kernel Test2-surrogate.c
rm -f Test2-common.o
cc -c  -g -I. -I../../runtime/c -I../../runtime/kernel Test2-common.c
rm -f Test3-surrogate.o
cc -c  -g -I. -I../../runtime/c -I../../runtime/kernel Test3-surrogate.c
rm -f Test3-common.o
cc -c  -g -I. -I../../runtime/c -I../../runtime/kernel Test3-common.c
rm -f client
cc  -g -I. -o client  clnt.o Test1-surrogate.o Test1-common.o \
  Test2-surrogate.o Test2-common.o Test3-surrogate.o Test3-common.o \
  ../../runtime/c/libilu-c.a ../../runtime/kernel/libilu.a 
rm -f srvr.o
cc -c  -g -I. -I../../runtime/c -I../../runtime/kernel srvr.c
rm -f Test1-true.o
cc -c  -g -I. -I../../runtime/c -I../../runtime/kernel Test1-true.c
rm -f Test3-true.o
cc -c  -g -I. -I../../runtime/c -I../../runtime/kernel Test3-true.c
rm -f server
cc  -g -I. -o server  srvr.o Test1-common.o Test1-true.o \
  Test2-common.o Test3-common.o Test3-true.o \
  ../../runtime/c/libilu-c.a ../../runtime/kernel/libilu.a
./testserver
Starting server...
Running client against server...
Client run successful.
Killing server...
./testserver: 27469 Terminated
Exiting with status 0.
% 
@end transcript

@item
If the build goes well, install the system with the command
@transcript
% @userinput{cd @metavar{ILUSRC}}
% @userinput{make Install}
@end transcript

@item
After the installation is complete, you may remove extra files in @metavar{ILUSRC}
with the command
@transcript
% @userinput{make Clean}
@end transcript
You may wish to use @command{make Clean} at any time, to get your
system into a consistent state.

@item
If you change the configuration files, you should clean the system with the command
`@command{make Clean}', and redo the installation starting at step 2.  If you run
into problems that can be fixed without changing the configuration files, you can re-build
the system by starting at step 3.
@end enumerate

@subsection Environment Variables

@system{ILU} tools use a number of @system{UNIX} environment variables under the covers.

@itemize @bullet
@item
The variable @var{ILUHOME} should be set to point to the value of @metavar{ILUHOME}.
@item
The variable @var{ILUPATH} should be set to a colon-separated list of
directories in which the tools look for interface files.  A minimal value for
@var{ILUPATH} is probably @code{.:$@{ILUHOME@}/interfaces}.
@item
Your @var{PATH}
environment variable should have the directory @file{@metavar{ILUHOME}/bin} on it.
@item
Your @var{MANPATH} variable should have the directory @file{@metavar{ILUHOME}/man} on it.
@item
If you are using @language{Common Lisp}, the portable DEFSYSTEM included with
@system{ILU} uses the value of @var{SYSDCLPATH} to find system descriptions.  It should
be a colon-separated list of directories.  A good initial value might be
@code{.:$@{ILUHOME@}/lisp}.  See Appendix A of the reference manual for more details on the portable
DEFSYSTEM.
@item
If you are using @language{Python}, the value of the environment variable @var{PYTHONPATH}
should include the directory in which the @module{ilu} library for
@language{Python} has been installed;
that's normally @file{@metavar{ILUHOME}/lib}.
@item
The variable @var{ISLDEBUG} can optionally be set to any value to enable tracing
in the @language{ISL} parser.
@item
The variable @var{ILU_DEBUG} can be optionally be set to a colon-separated list of
trace values to enable tracing in the @system{ILU} runtime kernel.  @xref{Debugging ILU Programs}, for more information.
@end itemize

@subsection Testing the Build

There are several ways to test the build.  The most straightforward is to build and install it somewhere.
Set up your environment variables as described above.
Then make a scratch directory, which we'll refer to as @metavar{TESTDIR}, and
do the following:

@transcript
% @userinput{cd @metavar{TESTDIR}}
% @userinput{cp @metavar{ILUHOME}/examples/test1/* .}
% @userinput{ilumkmf}
% @userinput{make client server}
@metavar{ILUHOME}/bin/c-stubber  Test1.isl
header file for interface Test1 to ./Test1.h...
common code for interface Test1 to ./Test1-common.c...
code for surrogate stubs of interface Test1 to ./Test1-surrogate.c...
code for true stubs of interface Test1 to ./Test1-true.c...
@metavar{ILUHOME}/bin/c-stubber  Test2.isl
header file for interface Test2 to ./Test2.h...
common code for interface Test2 to ./Test2-common.c...
code for surrogate stubs of interface Test2 to ./Test2-surrogate.c...
code for true stubs of interface Test2 to ./Test2-true.c...
@metavar{ILUHOME}/bin/c-stubber  Test3.isl
header file for interface Test3 to ./Test3.h...
common code for interface Test3 to ./Test3-common.c...
code for surrogate stubs of interface Test3 to ./Test3-surrogate.c...
code for true stubs of interface Test3 to ./Test3-true.c...
rm -f clnt.o
cc -c -g -I. -I@metavar{ILUHOME}/include  clnt.c
rm -f Test1-surrogate.o
cc -c -g -I. -I@metavar{ILUHOME}/include  Test1-surrogate.c
rm -f Test1-common.o
cc -c -g -I. -I@metavar{ILUHOME}/include  Test1-common.c
rm -f Test2-surrogate.o
cc -c -g -I. -I@metavar{ILUHOME}/include  Test2-surrogate.c
rm -f Test2-common.o
cc -c -g -I. -I@metavar{ILUHOME}/include  Test2-common.c
rm -f Test3-surrogate.o
cc -c -g -I. -I@metavar{ILUHOME}/include  Test3-surrogate.c
rm -f Test3-common.o
cc -c -g -I. -I@metavar{ILUHOME}/include  Test3-common.c
rm -f client
cc -g -o client clnt.o Test1-surrogate.o Test1-common.o \
  Test2-surrogate.o Test2-common.o Test3-surrogate.o \
  Test3-common.o  @metavar{ILUHOME}/lib/libilu-c.a \
  @metavar{ILUHOME}/lib/libilu.a
rm -f srvr.o
cc -c -g -I. -I@metavar{ILUHOME}/include  srvr.c
rm -f Test1-true.o
cc -c -g -I. -I@metavar{ILUHOME}/include  Test1-true.c
rm -f Test3-true.o
cc -c -g -I. -I@metavar{ILUHOME}/include  Test3-true.c
rm -f server
cc -g -o server srvr.o Test1-common.o Test1-true.o \
  Test2-common.o Test3-common.o Test3-true.o \
  @metavar{ILUHOME}/lib/libilu-c.a @metavar{ILUHOME}/lib/libilu.a
% @userinput{./server &}
[1] 7079
% exported ilu:Test1-Server/Test1_Initial_Object;ilu%3AiX2w6hjR-...
% @userinput{./client}
Test1.O1.U-CSS-to-U
u._d=5, u._u.boolean = 1, u._u.O1 = 0x1ffee7c
Test1.O1.f-CSS-to-R0
ro->i=9
Test1.O1.R-ScS-to-F
f=39.700001
Test1.O1.a-RO
Test1.O1.get-O2
got O2, sbh = ilu:Test1-SunRPC-Server/1;ilu%3AaUtts57Ywbp2fxe6+-...
Test1.o2.OO-A0-to-CSS
Test1.O2.R-I-A1-to-I-A0
Test1.O1.get-O3
making O3...
got O3, sbh = ilu:Test1-Server/2;ilu%3An+eRrvAZ8JB9v2qoX7sJGPxdX...
Test1.O3.RS-R-to-R-IS
Test1.O3.O1-U-to-U
u._d=3, u._u.boolean = 0, u._u.O1 = 0xd2b78
Test1.O1.get-O3
got O3, sbh = ilu:Test1-Server/3;ilu%3Ab-mNa9uj0TsJAp7YrlEh0AUfX...
Test3.O.RS-R-to-R-IS
Test3.O.O1-U-to-U(0xd7520, @{3@})
u._d=3, u._u.boolean = 0, u._u.O1 = 0xd2b78
Test3.O.I-to-Test1U(397)
Test3_O_I_to_Test1U:  u2._d=5, u2._u.boolean = 1, u2._u.O1 = 0x10a88d0
Test1.O1.get-O3
making O4...
got O3, sbh = ilu:Test1-Server/4;ilu%3Ad8sZGQLLpVsJ2PBL5BoIX45qO...
Test1.O4.R_to_R (12345.6789000000) => 1020304.0506070800
doubles:  r1 is 12345.6789000000, r2 is 1020304.0506070800
%
@end transcript

@noindent
You can proceed to test the various other clients and servers in different languages against
each other.  See the file @file{@metavar{ILUHOME}/examples/test1/README} for more information.

@subsection Notes on Specific Systems

@subsubsection HP/UX

From @code{hassan@@db.stanford.edu}:  ``In order to get ILU 2.0a to compile on HP/UX, I had to set the CC
environment variable to the following before running configure:  @code{setenv CC "/bin/cc -Aa +z -D_HPUX_SOURCE"}.''

@subsubsection DEC ALPHA with OSF OS

From @code{hassan@@db.stanford.edu}:  ``Use @program{cc} instead of @program{gcc} as the C compiler,
and make sure to include the `-taso' switch.''

From @code{jg@@w3.org}:  ``I built [ILU 2.0 alpha on OSF 3.2B] without the `-taso' switch.
Is this still needed?  @program{c-stubber} certainly ran without it this release.''

@subsubsection SunOS 4.1.x

Note that the default Sun C compiler is not @language{ANSI C}, nor is @program{gcc} when
installed against the normal Sun header files and @file{/lib/libc.a}.  You will have to use either
@program{gcc} with the GNU C Library @system{glibc}, or the SunPro @language{ANSI C} compiler @program{acc}, or Lucid Energize @program{lcc}, or some other ANSI compiler.

@section Examples

The following example uses of @ilu are provided in the installed
tree as subdirectories of @file{@metavar{ILUHOME}/examples/}:

@itemize @bullet
@item @file{tutorial} -- this contains the code for a small @ilu tutorial,
implemented in both @language{ANSI C} and @language{Python}.  If you are interested
in using either of these languages with @ilu, we suggest starting with the code
in this directory, and one of the files @file{@metavar{ILUHOME}/doc/tutorial-C.ps} and
@file{@metavar{ILUHOME}/doc/tutorial-Python.ps}.  Even if you want to use a different
programming language, it's probably worth your while reading one of these tutorials.
@item @file{test1} -- this contains our basic interoperability test program,
implemented in a number of languages.
If you are interested in working with @language{Common Lisp}, @language{Modula-3}, or @language{C++},
we recommend starting here.
@item @file{multlang} -- an example of using
multiple languages (@language{ANSI C} and @language{Python}) in the same address space, communicating via @ilu.
@item @file{blob} -- a contributed @language{Python} example that uses @system{Tk}.
@item @file{timeit} -- a crude timing test.
@end itemize

@noindent
Read the @file{README} file in each directory first.

@section Name Servers

No standard ``name service'' or binding service is provided.  We feel that this is an area
to be addressed independently, and we may include a name service in future releases of @system{ILU}.
An experimental simple name service bootstrap interface is available as the @dfn{simple binding system}.
See the @language{ANSI C} @C{ILU_C_PublishObject}, @C{ILU_C_WithdrawObject}, and @C{ILU_C_LookupObject},
and corresponding routines in the other languages, for more details.
This interface is not guaranteed to be present in future releases.

@section Documentation

@system{ILU} documentation is provided in a pre-formatted form, @language{PostScript}.  The source form
of the documentation is called @language{TIM}, and is documented in the @ilu reference manual.
If for some reason you do need to rebuild the documentation, you should have the systems @TeX{}, @language{Perl}, @system{ghostscript}, @program{dvips},
and @system{pbmplus}; if you can't find these yourself,
please send mail to @code{ilu-core@@parc.xerox.com} for info on how to find them.

@section Mailing Lists

To be added to, or deleted from, any ILU mailing list, please send mail to @code{ilu-request@@parc.xerox.com}.  @strong{Do not} send mail to the list itself.

The general ILU discussion mailing list is @code{ilu@@parc.xerox.com}.  People post questions, discuss changes, and help each other out on that list.  Another list, used only for announcements of ILU things, and consequently much lower-volume, is @code{ilu-interest@@parc.xerox.com}.  The @code{ilu} list receives everything that the @code{ilu-interest} list receives; there is no need to be on both lists.  Again, send mail to @code{ilu-request@@parc.xerox.com} to be added to or removed from either of these lists.

Archives of these lists can be found at @url{http://www-diglib.stanford.edu/ilu/"}.

@section Bug Reporting and Comments

@subsection Known Bugs and Gotchas

KNOWN BUGS:

Release 2.0alpha6:

1) [C++] The RemoveAll method on sequence objects uses a quadratic
algorithm rather than possible linear algorithm.

2) [configuration] Since our Makefiles are constructed via imake from
Imakefiles, which involves running the C preprocessor, watch out for use
of predefined C preprocessor symbols in pathnames!  Common boobytraps
include names of processors, vendors, and operating systems (e.g.,
"sparc", "sun", "hpux"), which are used (as isolated tokens according to
C rules) in some folks' conventions for naming directories.  If you're
lucky, you can solve these problems with quoting.  A more heavy-duty
approach is to #undef the offending macros at the start of
imake/ilu.defs.new, and re#define them at the end.

3) [kernel] UDP seems to currently have several bugs which render it
more than usually unreliable.

4) [kernel] There's no good way to control UDP timeouts.  The bad way
isn't declared in any header file.

5) [ISL] "TYPE X = OBJECT SUPERTYPES Y ...; TYPE Y = OBJECT
SUPERTYPES X ..."  crashes the parser (and thus
islscan and all the stubbers).  Don't do this!

6) [MOP] If ilu_AddRegisterersToDefault is used, callers of
ilu_Register@{Input,Output@}Source must be prepared for false callbacks.

7) [C++] stubber bugs noted in 1.8 bugs file have not been addressed.


@subsection Reporting Bugs

Report bugs (nah! -- couldn't be!) to the Internet address @code{ilu-bugs.parc@@xerox.com},
or to the XNS address @code{ILU-bugs:PARC:Xerox}.  Bug reports are more helpful with
some information about the activity; @emph{please} read @ref{Debugging ILU Programs},
for more information on how to look at problems.  General comments and suggestions can
be sent to either @code{ILU@@parc.xerox.com} or @code{ILU-bugs}.
