Issue 5942 in pharo: Core methods dependent on Compiler

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

Issue 5942 in pharo: Core methods dependent on Compiler

pharo
Status: Accepted
Owner: [hidden email]
Labels: Type-Seed Milestone-2.0

New issue 5942 by [hidden email]: Core methods dependent on  
Compiler
http://code.google.com/p/pharo/issues/detail?id=5942

Scanner -> (Symbol class>>#readFrom: "a CompiledMethod(459800576)")
CompiledMethodWithNode -> (ContextPart  
class>>#initializeTryNamedPrimitiveTemplateMethod "a  
CompiledMethod(92274688)")
Compiler -> (ContextPart  
class>>#initializeTryNamedPrimitiveTemplateMethod "a  
CompiledMethod(92274688)")
SyntaxErrorNotification -> (BasicCodeLoader>>#handleError: "a  
CompiledMethod(274989056)")
BlockLocalTempCounter -> (BlockClosure>>#numTemps "a  
CompiledMethod(738721792)")
ParserNotification -> (BasicCodeLoader>>#installSourceFile: "a  
CompiledMethod(292552704)")
Encoder -> (InstructionStream>>#willBlockReturn "a  
CompiledMethod(826277888)")




_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 5942 in pharo: Core methods dependent on Compiler

pharo

Comment #1 on issue 5942 by [hidden email]: Core methods  
dependent on Compiler
http://code.google.com/p/pharo/issues/detail?id=5942

- Probably BasicCodeLoader should be packaged separately from the  
commandLine
framework
- Then some of the other methods may be put as extension methods  
(#readFrom:, #iinitializeTryNamedPrimitiveTemplateMethod, #numTemps)

In InstructionStream, the other #willXXX methods refer to the bytecode  
integers directly.  BTW, the #willXXX methods have no senders :)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 5942 in pharo: Core methods dependent on Compiler

pharo

Comment #2 on issue 5942 by [hidden email]: Core methods dependent  
on Compiler
http://code.google.com/p/pharo/issues/detail?id=5942

I fixed the #willXXX methods.


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 5942 in pharo: Core methods dependent on Compiler

pharo
Updates:
        Labels: -Type-Seed Target-Seed Type-Cleanup

Comment #3 on issue 5942 by [hidden email]: Core methods dependent  
on Compiler
http://code.google.com/p/pharo/issues/detail?id=5942

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 5942 in pharo: Core methods dependent on Compiler

pharo
Updates:
        Labels: -Milestone-2.0

Comment #4 on issue 5942 by [hidden email]: Core methods dependent  
on Compiler
http://code.google.com/p/pharo/issues/detail?id=5942

(No comment was entered for this change.)


_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Reply | Threaded
Open this post in threaded view
|

Re: Issue 5942 in pharo: Core methods dependent on Compiler

pharo
Updates:
        Status: Closed

Comment #5 on issue 5942 by [hidden email]: Core methods dependent  
on Compiler
http://code.google.com/p/pharo/issues/detail?id=5942

it is unclear which have been solved and which not.

Please submit issues for each of them


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