Re: fix for CLASSPATH/classpath switch behaviour

[Nic Ferrier <nferrier at tapsellferrier dot co dot uk>]

Mark Wielaard <mark@klomp.org> writes:

> Hi, 
>  
> On Fri, 2002-02-08 at 05:48, Tom Tromey wrote: 
> >  
> > Does the Sun javac have a way to override the system class path? 
> > What is it? 
> That is called the Bootstrap classes in Sun speak and it is overriden 
> with the -bootclasspath (for javac) or -Xbootclasspath (for java). 
>  
> In Sun speak you have four different "class inputs". 
> - Bootstrap, the core classes defined with -(X)bootstrap 
> - Extension, jars used to resolve Classpath entries in jar Manifest 
>   files with -extdirs. 
> - User, added with -classpath to the above two. 
> - Source, used with javac -sourcepath to override the above. 
>  
> Recent versions of jikes also define these options. 
> From the jikes manual page: 
>  
>        Jikes has several options related to classpath  searching. 
>        The  -bootclasspath, -extdirs, and -sourcepath options are 
>        the same as in javac.  In addition to being  specified  on 
>        the command line, the environment variables BOOTCLASSPATH, 
>        EXTDIRS, and SOURCEPATH may also be used to specify values 
>        for  these  options,  respectively.   Jikes  also  has the 
>        -classpath option as  in  javac,  with  the  corresponding 
>        environment variable CLASSPATH.  The classpath may also be 
>        specified in the environment variable JIKESPATH,  although 
>        this use is discouraged.  If JIKESPATH and CLASSPATH coex­ 
>        ist, preference will  be  given  to  JIKESPATH.   A  value 
>        specified  on  the  command  line  will be always be given 
>        preference over the value  of  any  environment  variable. 
>        All  the  directories and files specified in these options 
>        or environment variables  must  be  in  a  colon-separated 
>        list, e.g., ".:$HOME/java/jre/lib/rt.jar". 

I'd like us to support all of these in gcj and in gij.


Nic