This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: -classpath switch patch
- From: Nic Ferrier <nferrier at tapsellferrier dot co dot uk>
- To: Per Bothner <per at bothner dot com>
- Cc: java-patches at gcc dot gnu dot org
- Date: 23 Feb 2002 13:30:48 +0000
- Subject: Re: -classpath switch patch
- References: <3C70D730.4000604@jatak.com> <3C7142F0.6050003@bothner.com><3C7169EE.4040903@waitaki.otago.ac.nz><87664u1kfx.fsf_-_@tf1.tapsellferrier.co.uk><3C7185DB.6040301@waitaki.otago.ac.nz> <3C718A7F.1060501@bothner.com><873czy1gxg.fsf@tf1.tapsellferrier.co.uk><15473.41698.385817.823287@makita.cygnus.com><87r8niz2pp.fsf@tf1.tapsellferrier.co.uk><3C71A5AF.2010608@waitaki.otago.ac.nz><15473.43041.412371.618641@makita.cygnus.com><87k7t8xmmb.fsf@tf1.tapsellferrier.co.uk><87n0y4knnd.fsf@creche.redhat.com> <3C76F474.9090105@bothner.com><3C77295A.5060504@bothner.com>
Per Bothner <per@bothner.com> writes:
> I took a look at jcf-path.c, and one thing led to another.
> Here is my patch to fix path processing. It supports
> --CLASSPATH as a synonym for --classpath; --bootclasspath,
> and --wholeclasspath in place of the current --CLASSPATH.
> I also fixed a logic problem, where jcf_path_init was
> called *after* option processing, not before. Finally,
> I changed "." to not be part of the "system" or built-in
> class, but as an default for the non-builtin path, following
> what JDK does.
>
> One question I have is whether this is overkill. Specifically,
> is there any real reason to have --wholeclasspath? I tend to
> think not, unless there is some signicant difference between
> --wholeclasspath PATH and --classpath PATH--bootclasspath "".
I can't see any reason for --wholeclasspath, it just seems to be
another confusing switch.
However, without it the Makefile logic will have to be altered (as
opposed to just a search and replace of -CLASSPATH / -wholeclasspath).
Nic