FogBugz (Case [Issue]10374) Compiler Opal - Add CompilerContext class

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

FogBugz (Case [Issue]10374) Compiler Opal - Add CompilerContext class

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

Case ID:      10374
Title:        Add CompilerContext class
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?10374

The whole compilation chain needs quite some information to be present along the whole chain. We have moved some into the AST (e.g. the class that is compiled for), but there is more

RIght now it is actally quite a mess... some of it will go away with better APIs, but there is still information that is needed along the whole compilation chain (requestor, for example).

Another type of information is which concrete visitor to use

Yet another are Pragmas: meta information to change the compilers behavior ("Do not inline!").

All this we can put into a CompilationContext and pass this one object along to whole toolchain.


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

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