Fred Gray wrote:
>
> It's a straightforward bootstrapping problem, and it's apparently already been
> solved once in the past. See the javadoc for Runtime.setSecurityManager():
>
>This was moved to Runtime so that Runtime would no longer trigger
>System's class initializer. Runtime doe
[Any further messages should probably go to only the classpath list, not
the ORP list.]
On Sun, Mar 24, 2002 at 08:56:23PM -0600, Fred Gray wrote:
> On Sun, Mar 24, 2002 at 05:27:25PM -0700, Eric Blake wrote:
>
> > Would it be worth
> > moving the default properties from System over to Runtime
On Sun, Mar 24, 2002 at 05:27:25PM -0700, Eric Blake wrote:
> Fred Gray wrote:
> > Issue 1: Calling methods in java.lang.System from the constructor of
> > java.lang.Runtime seems to cause a crash.
>
> What is the crash you are getting?
This is the one where ORP prints
No Java handlers foun
Fred Gray wrote:
>
> I think I've figured out the minimal hack to the current classpath CVS to
> work with ORP 1.0.9 (at least for programs of the complexity of "Hello world").
> Hopefully, this will give the people who understand ORP some ideas on how
> to fix things up properly.
>
> Issue 1:
I think I've figured out the minimal hack to the current classpath CVS to
work with ORP 1.0.9 (at least for programs of the complexity of "Hello world").
Hopefully, this will give the people who understand ORP some ideas on how
to fix things up properly.
Issue 1: Calling methods in java.lang.Syst
5 matches
Mail list logo
