How did you set up rbyaml to be used instead of the builtin yaml? I'm having a few issues (but I always have issues getting builtins to work right).On 6/2/06,
Ola Bini <[EMAIL PROTECTED]> wrote:Yep, it is now! =)
I'm planning on doing a minor release on sunday, with all the smallchanges done for t
Yep, it is now! =)
I'm planning on doing a minor release on sunday, with all the small
changes done for this. One problem is the SYCK bug, which generates
invalid YAML.
Right now I've hacked the definitions to allow illegal YAML.
/O
- Original Message -
From: Charles O Nutter <[EMAIL PR
It's shaping up to be a good summer.Is the latest code in rubyforge what works for installing rails? I'd like to play with that a bit.On 6/2/06, Ola Bini
<[EMAIL PROTECTED]> wrote:Hi again.
These last days I've been busy reimplementing the RbYAML Scanner inJava. The first implementation is very ro
Wow, that is insane! Insanely great
-Tom
On Sat, 03 Jun 2006, Ola Bini defenestrated me:
>
> Hi again.
>
> These last days I've been busy reimplementing the RbYAML Scanner in
> Java. The first implementation is very rough and unruly, but it's
> finished enough so I can measure performance
Hi again.
These last days I've been busy reimplementing the RbYAML Scanner in
Java. The first implementation is very rough and unruly, but it's
finished enough so I can measure performance. (The Scanner is the most
performance intensive parts of the YAML system).
For testing, I've taken a file cal
I believe clean may be ok, unless there's a ton of WeakReferences getting collected. clean repeatedly polls the ReferenceQueue for any collected references, removing them from ObjectSpace. According to JavaDocs and the 1.5
ReferenceQueue implementation, each poll should just pull the 'head' item o
On Friday 02 June 2006 00:14, Christopher Williams wrote:
> I had a few questions and comments. Have any of the patches that the
> students come up with made their way back into the trunk of JRuby?
Not yet, but if you want, I could create some patches for the position-fixes
and send them to the m
At 11:50 2006-06-02, you wrote:
>On Fri, 02 Jun 2006 09:22:29 +0200, Ola Bini wrote:
> > Regardig the ObjectSpace-implementation, I would recommend you to move the
> > cleanup call to ObjectSpace#iterator() ... I think that's where most of
> the
> > performance go through the roof.
> > And it's no
On Fri, 02 Jun 2006 09:22:29 +0200, Ola Bini wrote:
> Regardig the ObjectSpace-implementation, I would recommend you to move the
> cleanup call to ObjectSpace#iterator() ... I think that's where most of the
> performance go through the roof.
> And it's not like those WeakReferences are a problem.
Christopher Williams wrote:
> Thomas and Charles,
> I've been bad and haven't been subscribed to your development
> mailing list (I'm the RDT developer) - but I ran into some archives
> with questions and patches flying around by the Swiss students doing
> refactoring work.
>
> I had a few questio
Hi,
Regardig the ObjectSpace-implementation, I would recommend you to move the
cleanup call to ObjectSpace#iterator() ... I think that's where most of the
performance go through the roof.
And it's not like those WeakReferences are a problem...
/O
At 07:54 2006-06-02, you wrote:
>Scratch that t
FYI, the ObjectSpace performance hit appears to come from its use of a synchronized Set. If I modify it to use an unsynchronized Set, the numbers approach those when I have it completely disabled. Who says synchronization costs nothing?
The ObjectSpace thing is particularly interesting since it wou
Scratch that thing about synchronization...I think my numbers got mixed up. It's still slow with an unsynchronized Set.On 6/2/06, Charles O Nutter <
[EMAIL PROTECTED]> wrote:FYI, the ObjectSpace performance hit appears to come from its use of a synchronized Set. If I modify it to use an unsynchroni
13 matches
Mail list logo
