As mentioned last time, over the previous parts I at some point brutally broke our built in operators. I did so by actually implementing proper method calls.
It also made the compiler largely unusuable, and went unnoticed because, well, the compiler is still largely unusable.
...I published the last article in this series in June 2010, after a long break. At the time of finally making a serious start to this part, it was April 2013, and as of the time I am editing and putting the final touches on this, it is July 2013, and ...
First of all, here's the biggest reason I've been so excrutiatingly slow with getting this part together (at least that's my story, I guess I've had other things on my plate too...):
Tristan is 13 months now, and a real menace to my laptop (pulling off keys ...
Apologies for the delay... This part was ready before christmas, but for various reasons I never got around to posting it. And to make matters worse I managed to post the wrong part yesterday. Sigh.
Stepping back from the attr_*
debacle for a bit... I wanted to look ...
A couple of parts ago we established some of the problems with supporting even the seemingly simple attr_reader
, attr_writer
and attr_accessor
.
So far the method_missing implementation has just printed a notice and quit.
During the trip down the rabbit hole that is attr_accessor
and friends that became a major annoyance.
The problem is that this notice has not included a stack backtrace or any way to ...
I've been lazy lately... Well, not really, I've been extremely busy, but I ought to have fit this in earlier. It's gotten harder and harder to get done too, since it's now more work since I had to go back and figure out a lot of the reasons for what I'd ...
If you've been following the commits to the Github repository, you've already seen this go in... Specifically, this was the state as at the end of this post. Here's finally some ...
You may or may not have seen my recent post where I admitted to more or less having decided to make my compiler project a Ruby compiler. On the downside this means a lot of complexity that may make it harder to follow. On the upside... Well, you get to read ...