FogBugz (Case [Issue]10371) Compiler Opal - add #compiler to Behavior

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

FogBugz (Case [Issue]10371) Compiler Opal - add #compiler to Behavior

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

Case ID:      10371
Title:        add #compiler to Behavior
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?10371

In the current system, there is #compilerClass. But all users directly send new.

If we instead use #compiler (which returns a Compiler facade *object*), we can use
that for parametrizing the compiler in a subclass.

e.g.

comiler

^super compiler pragma: #noOptimize

will get you a standard compiler, but one that does not do any inlining (ifTrue and all).

Other things to be parametrized are

what concrete visititors to use for Semantic Analysis and Code Generation

IR backend

bytecode generator used

In addition, this is the place to change the parser and the pretty printer implementations. (this means it subsumes #prettyPrinterClass (already removed) and even #parserClass.


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=10371) from this case.

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