<mbj>
yorickpeterse: The parse.y whitequark created does not have C anymore
<yorickpeterse>
and since parse.y contains C code directly I'm not sure if that would work out
<yorickpeterse>
Though I'm not sure if I understand the use of parse.y since it emits C code, and not Ruby
2013-03-28
<whitequark>
yorickpeterse: you kinda can add SAX-style parsing to the parse.y's in the parser
<yorickpeterse>
I think I should show parse.y to every person that says code is self explaining
<yorickpeterse>
and it has docs, unlike parse.y
2013-03-24
<whitequark>
yorickpeterse: the absolutely worst part of parse.y is probably ternary op parsing
<whitequark>
yorickpeterse: soooo I think I have one last quirk of parse.y to dissect.
<whitequark>
yorickpeterse: do you know why the f parse.y has a distinct kDO_BLOCK token?
<yorickpeterse>
cat parse.y ?
<yorickpeterse>
I suppose it would be easier if you used the same drugs as the people that wrote parse.y
* yorickpeterse
grabs parse.y
2013-03-23
<yorickpeterse>
is this some crazy ritual needed to understand parse.y?
2013-03-22
<whitequark>
yorickpeterse: you said something about parse.y?
2013-03-21
<yorickpeterse>
because...parse.y
<yorickpeterse>
whitequark: we need to reverse engineer parse.y into a human readable set of documentation that can be used by everybody
<yorickpeterse>
no parse.y for me
2013-01-02
<yorickpeterse>
I'll quote myself: "Oh, I wonder how Ruby parses X. I'll take a look at parse.y!" - No one, ever
2012-12-13
<yorickpeterse>
found it: "Oh, I wonder how Ruby parses X. I'll take a look at parse.y!" - No one, ever
2012-11-29
<yorickpeterse>
"Oh, I wonder how Ruby parses X. I'll take a look at parse.y!" - No one, ever
<yorickpeterse>
It's just that I find that it's currently a bit hard to find solid documentation on the internals. The code itself is covered mostly but beyond that you'll quickly have to start diving into README.ext or parse.y
2012-08-29
<yorickpeterse>
parse.y isn't very helpful :?
2012-08-28
<judofyr>
yorickpeterse: well, parse.y is my best advice