2014-12-18

* yorickpeterse slaps himself around with a copy of parse.y

2014-12-11

<yorickpeterse> whitequark: https://github.com/matz/streem/blob/master/src/parse.y you wanna place bets on how long it takes for this parse.y to become huge?

2014-10-03

<yorickpeterse> A few patch levels in you'll finally understand everything of parse.y

2014-05-13

<yorickpeterse> Everything whitequark says should be taken with a grain of parse.y

2014-03-22

<yorickpeterse> tell me, how long did you spend digging around parse.y, translating documents, etc? :>

2014-02-21

<yorickpeterse> I also have a parse.y reference in a list

2013-07-30

<yorickpeterse> then again, I'm pretty sure nobody likes opening parse.y
<yorickpeterse> but this half-assed implementation isn't much better than cleaning up parse.y for once

2013-07-24

<yorickpeterse> adding "slaps X around with a copy of parse.y"

2013-07-23

<yorickpeterse> also why the fuck is this in fucking parse.y?

2013-06-18

<yorickpeterse> also pretty sure you can solve that by not dealing with parse.y every night before you go to bed

2013-05-06

<yorickpeterse> PARSE.Y MOTHERFUCKER
<yorickpeterse> teh parse.y

2013-04-24

<whitequark> yorickpeterse: and if we feed it parse.y?

2013-04-03

<yorickpeterse> Ruby well designed? *cough* parse.y

2013-03-30

<whitequark> yorickpeterse: there are tons of slightly different but essentially the same cases in parse.y
<yorickpeterse> unless parse.y works from outer to inner, instead of the other way around
<whitequark> yorickpeterse: defining a neat SAX interface for parse.y is going to be a lot of work :/
<whitequark> mbj: yorickpeterse: the author of whatever's in parse.y currently is not me
<mbj> yorickpeterse: The C that was in the parse.y did the lexing this one is C-free https://github.com/whitequark/ruby_parser/blob/master/lib/ruby18_parser.y
<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
<judofyr> yorickpeterse: parse.y