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]
