Re: trying to understand irb: why does it have its own lexer, instead of forwarding input to ruby ?
- From: "Joachim (München)" <wuttke1@xxxxxx>
- Date: 23 Jun 2006 10:13:16 -0700
Robert and Tim, thank you for your clear explanations.
As mentioned before, I want to extend the ruby language.
Specifically, I want to twist the interpreter so that it expands
for instance w8s6ny into w[8].s[6].y.size(). Do you experts
think this can be achieved by modifying IRB's ruby code,
without diving into Ruby's C code?
Kind regards, Joachim
.
- Follow-Ups:
- Re: trying to understand irb: why does it have its own lexer, instead of forwarding input to ruby ?
- From: Dave Burt
- Re: trying to understand irb: why does it have its own lexer, instead of forwarding input to ruby ?
- From: Tim Hoolihan
- Re: trying to understand irb: why does it have its own lexer, instead of forwarding input to ruby ?
- From: Robert Klemme
- Re: trying to understand irb: why does it have its own lexer, instead of forwarding input to ruby ?
- References:
- trying to understand irb: why does it have its own lexer, instead of forwarding input to ruby ?
- From: Joachim (München)
- trying to understand irb: why does it have its own lexer, instead of forwarding input to ruby ?
- Prev by Date: Re: Rails LiveCD
- Next by Date: Re: trying to understand irb: why does it have its own lexer, instead of forwarding input to ruby ?
- Previous by thread: Re: trying to understand irb: why does it have its own lexer, instead of forwarding input to ruby ?
- Next by thread: Re: trying to understand irb: why does it have its own lexer, instead of forwarding input to ruby ?
- Index(es):
Relevant Pages
|
