Issue 5819 in pharo: first iteration on moving fileIn users to new codeImporter

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

Issue 5819 in pharo: first iteration on moving fileIn users to new codeImporter

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

New issue 5819 by [hidden email]: first iteration on moving  
fileIn users to new codeImporter
http://code.google.com/p/pharo/issues/detail?id=5819

I'll publish a slice with:

- some cleanings to fileIn usages
- some fileIn users moved to use CodeImporter
- some fixes to the CodeImporter that raised when testing the two points of  
above.


_______________________________________________
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 5819 in pharo: first iteration on moving fileIn users to new codeImporter

pharo
Updates:
        Status: FixReviewNeeded

Comment #1 on issue 5819 by [hidden email]: first iteration on  
moving fileIn users to new codeImporter
http://code.google.com/p/pharo/issues/detail?id=5819

A bunch of small stuff.  I've run the tests of the whole image and noticed  
that I've plenty of nonHealthyDictionaries, but I'm not sure what caused  
it :/

Name:  
SLICE-Issue-5819-first-iteration-on-moving-fileIn-users-to-new-codeImporter-GuillermoPolito.1
Author: GuillermoPolito
Time: 5 May 2012, 11:57:13.422 pm
UUID: 160e0c7d-0b9f-45ea-9cda-30e31eb21184
Ancestors:
Dependencies: CodeImport-GuillermoPolito.4,  
CodeImport-Tests-GuillermoPolito.4, System-Changes-GuillermoPolito.136,  
Compiler-GuillermoPolito.329,  
Multilingual-TextConversion-GuillermoPolito.28,  
System-CommandLine-GuillermoPolito.14, Tests-GuillermoPolito.372,  
System-Installers-GuillermoPolito.14

issue  
http://code.google.com/p/pharo/issues/detail?id=5819&thanks=5819&ts=1336254855.

filein cleansing


_______________________________________________
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 5819 in pharo: first iteration on moving fileIn users to new codeImporter

pharo
Updates:
        Status: Workneeded

Comment #2 on issue 5819 by [hidden email]: first iteration on moving  
fileIn users to new codeImporter
http://code.google.com/p/pharo/issues/detail?id=5819

would be nice to deprecate old #fileIn methods (not remove them in first  
iteration)
what also would be nice is to replace fileIn method implementations with  
calls to your stuff :)


_______________________________________________
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 5819 in pharo: first iteration on moving fileIn users to new codeImporter

pharo
Updates:
        Status: FixToInclude

Comment #3 on issue 5819 by [hidden email]: first iteration on moving  
fileIn users to new codeImporter
http://code.google.com/p/pharo/issues/detail?id=5819

he, I misunderstood the range of your changes... it is ok to include like  
this and deprecate used #fileIn methods in a 2nd step


_______________________________________________
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 5819 in pharo: first iteration on moving fileIn users to new codeImporter

pharo
Updates:
        Status: Integrated

Comment #4 on issue 5819 by [hidden email]: first iteration on  
moving fileIn users to new codeImporter
http://code.google.com/p/pharo/issues/detail?id=5819

in 2.0 067


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