Re: [Jruby-devel] Questions about some AST nodes

2006-05-24 Thread Mirko Stocker
On Thursday 25 May 2006 02:03, David Corbin wrote: > > - MatchNode > > print 'x' if (/pattern/) That worked, thanks :-) > > - Match2Node > > print 'x' if $y =~ /pattern/ This produces only a Match3Node. > > - OpAsgnNode > > "x = 7" And this is just a LocalAsgnNode. > > - Spl

Re: [Jruby-devel] Questions about some AST nodes

2006-05-24 Thread David Corbin
On Wednesday 24 May 2006 06:45 pm, Mirko Stocker wrote: > Hi! > > I'm currently implementing a visitor which creates sourcecode from the > jruby-ast (we need this for our refactorings). I've implemented most nodes, > but I'm stuck with some. I would be very glad if someone could give me some > code

[Jruby-devel] Questions about some AST nodes

2006-05-24 Thread Mirko Stocker
Hi! I'm currently implementing a visitor which creates sourcecode from the jruby-ast (we need this for our refactorings). I've implemented most nodes, but I'm stuck with some. I would be very glad if someone could give me some code with the following nodes: - MatchNode - Match2Node - OpAsgnNod

Re: [Jruby-devel] Status on RbYAML.

2006-05-24 Thread Ola Bini
This sounds super promising. If your pure parser ends up beating the RACC one with lower memory (plus easier to read) that would be a big plus by itself. If the most intense part is the scanner and we Java-ize it, then I bet things speed up quite a bit more. One question I have is how yo

Re: [Jruby-devel] Status on RbYAML.

2006-05-24 Thread Thomas E Enebo
On Wed, 24 May 2006, Ola Bini defenestrated me: > > I've spent the last few days doing a major reworking on RbYAML. I've > rewritten the parser completely, and changed some other stuff too. Right > now I'm in a profiling/optimization-cycle for the load-path, and it looks > pretty promising. Rig

[Jruby-devel] Status on RbYAML.

2006-05-24 Thread Ola Bini
So. I've spent the last few days doing a major reworking on RbYAML. I've rewritten the parser completely, and changed some other stuff too. Right now I'm in a profiling/optimization-cycle for the load-path, and it looks pretty promising. Right now the loading is about 10-15% slower than the J