harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Fursov" <mike.fur...@gmail.com>
Subject Re: [drlvm] the big soup of VM properties (HARMONY-1626)
Date Tue, 10 Oct 2006 12:01:20 GMT
IMO "vm.dlls" property is useless today and should be removed at all. So we
need more precise example :)
+ I do not actually feel the difference between -X and -D options. Could
anyone explain when it's better to use -X and when -D?

On 10/10/06, Evgueni Brevnov <evgueni.brevnov@gmail.com> wrote:
>
> I don't think it is good idea to use -Dvm.dlls for setting up DRLVM
> specific properties. It should be much safer to use somthing like
> -Xvm.dlls. In that case it is really user's responisbility.
>
> Evgueni
>
> On 10/10/06, Mikhail Fursov <mike.fursov@gmail.com> wrote:
> > Dmitry,
> > Why do we need to hide the properties like "vm.dlls"? Once user
> overrides it
> > - he becomes responsible for a probable application failure.
> >
> > For example all of JIT properties are passed like system properties and
> it's
> > very convenient to override the default ones as command line parameters.
> >
> > On 10/10/06, Dmitry Yershov <dmitry.yershov@gmail.com> wrote:
> > >
> > > 2006/10/10, Mikhail Fursov <mike.fursov@gmail.com>:
> > > > On 10/10/06, Alexey Varlamov <alexey.v.varlamov@gmail.com> wrote:
> > > > >
> > > > > I think there is correlation between these 2 questions :). If we
> use
> > > > > "const char*", we simply copy key and value when setting a
> property.
> > > > > And this is impossible with void*.
> > > >
> > > >
> > > > Ok, this way it does works!
> > > >
> > > > BTW, there is alternative functionality named VMLocalStorage - so
> why
> > > > > make properties competing with VMLS? Do we really need "hidden"
> > > > > properties?
> > > >
> > > >
> > > > +1. Want to know the answer.
> > >
> > > Seems, that we need "hidden" properties.
> > >     Users can define any properties through command line
> -D<key>=<value>.
> > > Our VM has a set of "dangerous" properties (vm.dlls, vm.ee_dlls,
> > > vm.other_natives_dlls ...). We should hide their from users because
> > > redefining of their may lead to a crush. On the other hand users can
> > > define such properties and they should be visible for java
> applications.
> > >
> > > If You know other solution, lets discuss it.
> > >
> > > Dmitry
> > >
> > > >
> > > > --
> > > > Mikhail Fursov
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > Terms of use : http://incubator.apache.org/harmony/mailing.html
> > > To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> > > For additional commands, e-mail: harmony-dev-help@incubator.apache.org
> > >
> > >
> >
> >
> > --
> > Mikhail Fursov
> >
> >
>
> ---------------------------------------------------------------------
> Terms of use : http://incubator.apache.org/harmony/mailing.html
> To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
> For additional commands, e-mail: harmony-dev-help@incubator.apache.org
>
>


-- 
Mikhail Fursov

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message