FogBugz (Case [Issue]10378) Compiler Opal - There are 44 direct references to Scanner

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

FogBugz (Case [Issue]10378) Compiler Opal - There are 44 direct references to Scanner

Pharo Issue Tracker
A FogBugz case was assigned to Everyone by Clement Bera.

Case ID:      10378
Title:        There are 44 direct references to Scanner
Status:       Work Needed (Conclusion)
Category:     Bug
Project:      Compiler Opal
Area:         Misc
Priority:     6 - Fix If Time
Milestone:    Pharo3.0: 30/03/2014
Assigned To:  Everyone

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


Changes:
Status changed from 'Work Needed' to 'Work Needed (Conclusion)'.
Milestone changed from 'Later' to 'Pharo3.0: 31/03/2014'.

Basically all the references to scanner were (directly or indirectly) :
Scanner new scanTokens: aString

So I created method :
String>>#parseAsLiteralToken
^ Scanner new scanTokens: self

So now we have 1 references to Scanner left in String>>#parseAsLiteralToken.

Now we can work on the real problem, implementing RBParser>>#scanTokens:

Slice in inbox


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

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