multiple assignment not using to_ary on non-array elements being multiassigned
--
Key: JRUBY-1178
URL: http://jira.codehaus.org/browse/JRUBY-1178
Project: JRuby
Issu
Error messages _still_ report incorrect line number (off by 1)
--
Key: JRUBY-1177
URL: http://jira.codehaus.org/browse/JRUBY-1177
Project: JRuby
Issue Type: Sub-task
Compo
Charles Oliver Nutter wrote:
Attached is a patch that alters yield to always accept IRubyObject[],
like a normal call, and changes all callers and implementations to
handle that fact. There are ups and downs to this:
I committed the patch; I'm trying to work the kinks out of the
compilation p
Nick Sieger 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
working. As far as
dertown wrote:
Is there a place where we can start getting some requiremnts together for a
new Ruby Security implentation. Then it would be possible to completely
replace SAFE and Taint.
Would people want to use the same api if possible?
Well right here on the list would be a great start.
(Regexp) StringScanner.scan_until doesn't work properly after
StringScanner.skip is called
--
Key: JRUBY-1176
URL: http://jira.codehaus.org/browse/JRUBY-1176
Proj
Would this solution be able to to cross implentations of Ruby?
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
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
working. As far as I can tell tainting
Thomas E Enebo wrote:
>
> On 6/28/07, dertown <[EMAIL PROTECTED]> wrote:
>> Thomas E Enebo 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 demo
build-config.xml also should be updated
---
Key: JRUBY-1175
URL: http://jira.codehaus.org/browse/JRUBY-1175
Project: JRuby
Issue Type: Bug
Components: Compiler
Reporter: Changshin Lee
There are many IO operations(database) in mingle test, so the
proportion of improvement is decreased.
From bench_method_dispatch.rb, the improvement is 5-10%. Of course,
it's also a special case.
On the other hand, JRuby use intern to compare to String with "==" in
many places, so the improveme
I have always, as have many of you, hated the fact that Block.yield
accepts a RubyArray. There are reasons for this, though they're not
particularly good..
When yielding values to a block, if you yield an array directly it will
be implicitly splatted into the target arguments. It's somewhat
i
12 matches
Mail list logo
