2006/10/10, Evgueni Brevnov <[EMAIL PROTECTED]>:
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.
I tend to agree - we have freedom to extend command line options and satisfy both ordinary user and VM configurator convenience. Then indeed we need to separate storage... Maybe use "-XDkey=value" syntax for VM-specific properties? Mikhail, BTW, what would you say if all JIT-specific properties were kept separately? E.g. if there were JAVA, VM, JIT types of properties storage, would it be of some convenience to JIT side? Just curious :)
Evgueni On 10/10/06, Mikhail Fursov <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> wrote: > > > > 2006/10/10, Mikhail Fursov <[EMAIL PROTECTED]>: > > > On 10/10/06, Alexey Varlamov <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Mikhail Fursov > > --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
