There’s not too much reading to do at the moment, at least on the
Cardinal front. I’m hoping to make a first, preliminary release over
the weekend which will include an overview of the design as it stands
ATM.
Before I have a chance of understanding the project, I’ll have to brush
up my C, and read up on VMs and stuff. I don’t come from a CS
background, hence many many many gaps in my knowledge. So I do have a
lot of reading to do.
Concerning this and the discussion about what parser to use I’d say that
what we really need is to decide on a common AST representation for
Ruby. Then we can have different parser front-ends generating the
correct type of AST and have different analysis and code generation
back-ends.
Yes, quite true.
I’d say that in general though it’s not the design of this or the
parsing that is the hard part; these things are pretty standard in
CS/compiler construction; the hard part is what kind of run-time support
is needed (and of course how you implement it) for Ruby semantics.
Right, like how do you deal with eval - it should be doable in the runtime
lib.
Yes, but also the semantics of normal class creation, method additions
etc, what makes Ruby Ruby…
BTW, I have two thesis students working (they’ll be starting in 3 weeks
actually) on Ruby compilers, one for compiling to MSIL/CIL and one for
compiling to llvm. Would be great if all these different Ruby compiler
projects could eventually share code although I think it’s too early for
that at this point…
That’s great we’ve got grad student slaves working on a Ruby compiler
They’re mid-level thesis so it’s two 10 week projects but yes, basically
you’re right ;). The goal is to get two prototypes that covers some
small part of Ruby to show if/how it’s feasible to do it. Based on that
one can decide how to proceed.
But seriously, this sounds like a great time to coordinate efforts. I’m
not sure it’s too early to do that.
Coordinate by creating common AST format I’d say, the rest is not clear
how much overlap it’s going to be imho.
BTW: What’s llvm?
http://llvm.cs.uiuc.edu/
Compiler infrastructure with abstract assembly language which they can
generate different machine codes from => we can abstract away from
back-end; if we just generate llvm assembly they take care of the
CPU-specific stuff.
I’m sure this has appeared earlier in the thread, but I can’t find
it…where is Ruth currently hosted? I would like to download it.
I’ve been doing some work with Ripper and would like to see your AST
format.
Thanks,
Chad
···
On Feb 29, 2004, at 3:19 PM, Robert Feldt wrote:
It was some time since I touched Ruth now but if I remember correctly
it had a fairly complete Ruby AST in there. I propose you at least
check it out…
Until now, the FreeRIDE debugger did not work under windows.
We now have a
maintenance release of FreeRIDE for Windows with a working
debugger! Many
thanks for Mark Watson for discovering the solution.
It does still not work. The maximum was 3 single step commands before
it crashed.
I can’t reproduce this problem. Does it happen consistently? Can
you send me
a small sample program to debug and set of steps to reproduce
the problem?
Is anyone else having a similar problem, as well??
Yes, I can’t seem to debug any programs in latest FreeRide. Maybe I’m
doing something wrong. Error messages same as Lothars.
Hmmm… I’m going to have to try this on a clean system. What version of
windows are you running?
I’m still having problems with my scroll-wheel (have been since 0.49, I
think it was). I can scroll down, but if I scroll up, it just keeps going
up until I move the mouse-wheel again (in either direction), in which case
it warps back down to where I started (plus or minus a line or two).
I wouldn’t mind trying to fix it myself, but I have no idea where begin…
http://llvm.cs.uiuc.edu/
Compiler infrastructure with abstract assembly language which they can
generate different machine codes from => we can abstract away from
back-end; if we just generate llvm assembly they take care of the
CPU-specific stuff.
That sounds a bit like the Intermediate Compiler Code, which is an
abstract assembly language for compilers that target Parrot.
It was some time since I touched Ruth now but if I remember correctly
it had a fairly complete Ruby AST in there. I propose you at least
check it out…
I’m sure this has appeared earlier in the thread, but I can’t find
it…where is Ruth currently hosted? I would like to download it.
I’ve been doing some work with Ripper and would like to see your AST
format.
Until now, the FreeRIDE debugger did not work under windows.
We now have a
maintenance release of FreeRIDE for Windows with a working
debugger! Many
thanks for Mark Watson for discovering the solution.
It does still not work. The maximum was 3 single step commands before
it crashed.
I can’t reproduce this problem. Does it happen consistently? Can
you send me
a small sample program to debug and set of steps to reproduce
the problem?
Is anyone else having a similar problem, as well??
Yes, I can’t seem to debug any programs in latest FreeRide. Maybe I’m
doing something wrong. Error messages same as Lothars.
Hmmm… I’m going to have to try this on a clean system. What version of
windows are you running?
Hmmm… I’m going to have to try this on a clean system. What version of
windows are you running?
Win XP Pro with SP1 but I have to retract from this bug report. After a
restart things now seem to be working ok. I was too fast on the trigger
there. I can now let my students loose on FreeRIDE; I’m sure they’ll
find (and report to me! :)) any problems…
Sorry for the delay in responding (posting to the FreeRIDE Users mailing
list would probably work better).
I’m still having problems with my scroll-wheel (have been since 0.49, I
think it was). I can scroll down, but if I scroll up, it just keeps going
up until I move the mouse-wheel again (in either direction), in which case
it warps back down to where I started (plus or minus a line or two).
I wouldn’t mind trying to fix it myself, but I have no idea where begin…
We use FXScintilla as the editing component, so the problem would probably
lie either in FXSCintilla itself, or in the way the FreeRIDE interfaces to
it. I’ll add this to our bug list. If you want to look for it yourself,
start with the FXScintilla files in:
FreeRIDE\plugins\rubyide_fox_gui\fxscintilla
Also, where can I change the syntax coloring?
Look in the same directory I listed above. Look at global_properties.rb
and ruby_colourize.rb.
Hmmm… I’m going to have to try this on a clean system. What version of
windows are you running?
Win XP Pro with SP1 but I have to retract from this bug report. After a
restart things now seem to be working ok. I was too fast on the trigger
there. I can now let my students loose on FreeRIDE; I’m sure they’ll
find (and report to me! :)) any problems…
Fantastic! Of course, when they do find problems, it would be better to
report them on the FreeRIDE Users’s ML, than here.