Alan McKean wrote:
Thanks for taking the time to think this through. Let me make sure I
understand. What you are proposing would decouple the runtime from the
objects but still make it accessible via the ClassLoader. That seems to
be solve a major part of the problem, but doesn't it still leave
2007/7/4, Charles Oliver Nutter <[EMAIL PROTECTED]>:
dreamhead wrote:
> Hi, Charlie!
>
> MethodIndex in compiler is worth considering.
>
> The following code is from invokeDynamic of StandardASMCompiler.
> int index = MethodIndex.getIndex(name);
> ...
> if (index != 0) {
>invokeUtilityMethod(
Visibility issues: top level object always stays private and Module.new {}
doesn't use public visibility for block body
---
Key: JRUBY-1185
URL: ht
Thanks for taking the time to think this through. Let me make sure I
understand. What you are proposing would decouple the runtime from
the objects but still make it accessible via the ClassLoader. That
seems to be solve a major part of the problem, but doesn't it still
leave the metaclass
Thanks for taking the time to think this through. Let me make sure I
understand. What you are proposing would decouple the runtime from
the objects but still make it accessible via the ClassLoader. That
seems to be a major part of the problem, but doesn't it still leave
the metaclass hierar
dreamhead wrote:
Hi, Charlie!
MethodIndex in compiler is worth considering.
The following code is from invokeDynamic of StandardASMCompiler.
int index = MethodIndex.getIndex(name);
...
if (index != 0) {
invokeUtilityMethod("doInvokeDynamicIndexed", callSigIndexed);
In new MethodIndex, index
On 7/3/07, dertown <[EMAIL PROTECTED]> wrote:
I started a Wiki Page for the new Security features/implemenation at the
Jruby wiki.
how would the Sandbox work in ruby and can it be be cross ruby
implemntation?
Why wrote the original implementation, you can read about it here:
http://code.why
Nick Sieger-2 wrote:
>
> On 6/28/07, Thomas E Enebo <[EMAIL PROTECTED]> wrote:
>> I say chuck it out since we are not even close to being correct in
>> this area. It gives a false sense of security. In fact, I wonder
>> what sort of audit MRI goes through to demonstrate that safe/taint is
>>
Hi, Charlie!
MethodIndex in compiler is worth considering.
The following code is from invokeDynamic of StandardASMCompiler.
int index = MethodIndex.getIndex(name);
...
if (index != 0) {
invokeUtilityMethod("doInvokeDynamicIndexed", callSigIndexed);
In new MethodIndex, index is always greater
""[0...-1] returns nil instead of ""
Key: JRUBY-1184
URL: http://jira.codehaus.org/browse/JRUBY-1184
Project: JRuby
Issue Type: Bug
Components: Core Classes/Modules
Affects Versions: JRuby 1
Charles Oliver Nutter wrote:
Thoughts? More ideas?
More ideas!
A different approach, less brute-force, but requires control over the
deserialization process (perhaps that's not too much to ask?)...
RubyObject.java:
public void readExternal(ObjectInput in) throws IOException,
Alan McKean wrote:
Since the lack of Java serialization of JRuby objects stops us dead in
our tracks when trying to hook up our persistence engine, I am
interested in either getting someone on this end to work on it or
jumping in myself. In either case, I need some background on the JRuby
runt
12 matches
Mail list logo
