Improve the parser to detect syntax errors
Reported by Chris Corbyn | December 11th, 2008 @ 03:08 PM
I can throw a lot of invalid syntax into a .j file and it will run without even a warning. Surely syntax errors should be of the highest possible severity?
It's quite scary to think that a well meaning parser can discard things I write in my source code without even mentioning it.
It also makes me wonder if the parsing could be a lot more efficient.
Would you guys like some input in this area? I'm not an expert but I know a little bit about LALR(1) grammars and lexical analysis (another area of the source that looks like it could use some improving - long piped regexes are generally slower than checking several smaller regexes and switching states).
Clearly it's a hugely complex area but it's certainly something that needs to be as close to 100% spot-on as possible :)
Comments and changes to this ticket
-
-
Chris Corbyn December 12th, 2008 @ 01:01 AM
Ok, no promises but I'll give it a shot and see if I can provide a patch.
-
Ross Boucher May 5th, 2009 @ 11:38 AM
- Tag changed from “lexer, objective-j, parser, preprocessor” to “@acknowledged, lexer, objective-j, parser, preprocessor”
Any progress here? The ticket has been moved to github, so comment there please:
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
The Cappuccino Web Framework, including AppKit, Foundation, and Objective-J.
Chris Corbyn
Ross Boucher