parse error on value ":" (tCOLON) | could not parse

[presidentbeef]

parse error on value ":" (tCOLON) | could not parse

[presidentbeef]

Yeah, it's ruby parser. I did some minor monkeypatching to help it out, but it's not enough. Hopefully there will be a release with 1.9 syntax support soon. I've considered vendoring it, but it seems like a pain.

On the other hand, I think it's silly that Rails will generate 1.9 syntax if you happen to use 1.9 and 1.8 syntax otherwise. Kind of a weird thing to do.

[oreoshake]

Yeah that's like when you see a hash like:

asdf = {:something => 'asdf', asdf: 'something'} wtf

Justin wrote:

Yeah, it's ruby parser. I did some minor monkeypatching to help it
out, but it's not enough. Hopefully there will be a release with 1.9
syntax support soon. I've considered vendoring it, but it seems like a
pain.

On the other hand, I think it's silly that Rails will generate 1.9
syntax if you happen to use 1.9 and 1.8 syntax otherwise. Kind of a
weird thing to do.

---

Reply to this email directly or view it on GitHub:
#20 (comment)

[presidentbeef]

Okay, I have a local copy of ruby_parser working with Brakeman, and it parses the Rails 3 generated files. Need to test some more to make sure I don't run into problems with the gem version.

Edit: I mean the ruby_parser gem will be installed because of dependencies that Brakeman has. I need to make sure the gem does not get loaded and cause conflicts with the local version.

[presidentbeef]

Okay, this should be all fixed now. Thanks!

[oreoshake]

Confirmed. Thanks!

Justin wrote:

Okay, this should be all fixed now. Thanks!

---

Reply to this email directly or view it on GitHub:
#20 (comment)

[samstickland]

+1