FogBugz (Case [Issue]10373) Compiler Opal - instead of #parserClass, everyone should use the Compiler Frontend

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

FogBugz (Case [Issue]10373) Compiler Opal - instead of #parserClass, everyone should use the Compiler Frontend

Pharo Issue Tracker
A FogBugz case was opened by Marcus Denker.

Case ID:      10373
Title:        instead of #parserClass, everyone should use the Compiler Frontend
Status:       Work Needed
Category:     Bug
Project:      Compiler Opal
Area:         Misc
Priority:     3 - Must Fix
Milestone:    Later
Assigned To:  Everyone

URL:          https://pharo.fogbugz.com/default.asp?10373

there are two uses for #parserClass

==> parseSelector:

==> parsing to an AST in the context of a class *and* correct error handling assumed

For the last one, this is exactly what the Compiler frontend is for.

we then use #compiler for parseSelector, too. 

After that, we do not need #parserClass anymore.


You are subscribed to this case.  If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=10373) from this case.

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker