Properties

[Anthony Green]

Jeff wrote:
> So far we have three proposals:
> 
>   1) Add a properties section to the ELF image
>   2) Command-line arguments to gij, modify classloader
>      to load compiled classes
>   3) Environment variables

I would replace (1) with...

    1a) Bind properties to executable after linking with gcjprop.
    1b) Bind properties to executable before linking with -D.

1b may use the same section trick, but as Kresten pointed out, it
might also be useful to not have to reply on this trick, and have some
other way for jvgenmain to make the data available.  A simple
configure test could figure this out.

Here's my guess as to the order these should be implemented in: 3, 1b,
1a, 2.

The trick with 3 is to come up with some standard variable names.
Unfortunately, you can't use `.' in environment variables on some
systems.  What to do?  Replace them with `_' so, maybe, GCJ_java_home
maps to java.home?

The other thing to worry about is what takes precedent?  Built in
properties?  Command line properties?  Environment variables?
My suggestion, in decreasing priority order is:

	1 - command line (on gij)
	2 - environment variable
	3 - built in

AG

-- 
Anthony Green                                               Cygnus Solutions
                                                       Sunnyvale, California