Re: [Sablevm-developer] Re: Compile issue

[Etienne M. G. <eg...@j-...>]

Hi Brent.

Brent Fulgham wrote:
> Ack!  So I have.  Attaching now.

The patch looks OK.  (It's definitely not what I would keep in the final
optimized version of SableVM, but it looks operational).

Now, we have the choice of either using it, or fixing --class-path using
an application class loader (which is the right way to implement the
whole thing).

Would you like to work on the application class loader?

I would still consider your patch, in the short term, as it can be
convenient for testing.

What do you think?

> Right -- I don't think this patch handles all such cases properly,
> since it adds an extra '/' to the patch.  This is, of course,
> easy to fix.  Although in practice I think the use of
> "[...]sablepath/classes//" just happens to work on most systems.

In fact, if we really want to be system independent, we need to use
system properties for this.  All this is best done in Java, using an
application class loader.

> Right -- with compile-time option so we don't always have to
> pass it as a boot parameter.  Then --class-path would direct the
> loader to our standard set of paths for classes.

Hmmmm, why not in "/etc" (this path would be a compile time constant, as
I already do with the license files).  I would very much like sablevm to
use configuration files, instead of environment variables, to find its
default boot paths.  Much cleaner.

Etienne
-- 
----------------------------------------------------------------------
Etienne M. Gagnon, M.Sc.                     e-mail: eg...@j-...
Author of SableCC:                 http://www.sable.mcgill.ca/sablecc/
and SableVM:                                   http://www.sablevm.org/
----------------------------------------------------------------------