In Sun, 8 Jul 2001, Edward Avis cum veritate scripsit :
> >Actually they WILL clash!
>
> Huh?
Yeah! ;-)
> import com.snakeoil.palisade.*;
>
> or
>
> import com.gerbil-gratings.simphoni.*;
>
> There's no problem unless you mix the two.
Example:
My Program uses LIBOLD (com.firm.lib) and I also use programs which need
LIBNEW (also com.firm.lib). CLASSPATH is LIBNEW:LIBOLD:other.
My other programs will run but not my own program.
As an actual example at least JMF with its changes but same namespace will
cause such pbs.
(just for information for other readers who doesn't know much about the
practical use of this nice language called Java... ;-) )
[...]
> If you deliberately want to keep using an older version for some things,
Actually there are cases where I *must* keep old versions (i.e. for
customers) and new versions (i.e. for research) both in use.
> and a newer version for others, probably the best strategy is to have
> one installed system-wide, one in your home directory, and change the
> CLASSPATH as needed. This is the same as what you'd do with .so files,
> C header files, Perl modules or whatever.
That's what I do all the time (supported by different targets in makefiles
etc.).
But that's should not happen to the guy with his shiny new linux...
;-(
Frank
--
Sending unsolicited commercial email to this address may be a violation
of the Washington State Consumer Protection Act, chapter 19.86 RCW.
Frank Meurer <[EMAIL PROTECTED]>, PGP ID: 0x5E756DA8
Key fingerprint = 169A 1138 8DB4 528F 2F01 20A6 EDD8 49C3 5E75 6DA8
