January 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Finding all places where a class is instantiated?

by Mariano Martinez Peck

On Sun, Jan 15, 2012 at 7:10 PM, Stefan Marr <smalltalk(a)stefan-marr.de>wrote: > Hi: > > On 15 Jan 2012, at 19:06, StÃ©phane Ducasse wrote: > > > Stefan why Shift+N is not enough for you? > > Shift+N? I assume you refer to cmd+n on a Mac, which gives me all senders. > No. cmd + shift + n gives you the list of references to a class. > Well, senders of #new is not exactly helpful. > > Best regards > Stefan > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > > > -- Mariano http://marianopeck.wordpress.com

Jan. 15, 2012

Re: [Pharo-project] Finding all places where a class is instantiated?

by Stefan Marr

Hi: On 15 Jan 2012, at 19:06, StÃ©phane Ducasse wrote: > Stefan why Shift+N is not enough for you? Shift+N? I assume you refer to cmd+n on a Mac, which gives me all senders. Well, senders of #new is not exactly helpful. Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Jan. 15, 2012

Re: [Pharo-project] Finding all places where a class is instantiated?

by StÃ©phane Ducasse

But I imagine that you can find these just looking at the users of the classes. The strength of RBPaserTreeSearcher is when you want to get a specific method invocation and rewrite it. Stefan why Shift+N is not enough for you? Stef > Depends on how you use your classes. > > If you have have a finite set of constructor methods you can use > 'Refactor > Search code...' with something like this: > > RBParseTreeSearcher new > matches: 'PluggableButtonMorph on: `@.arg1' do: [ :node :answer | node ]; > matches: 'PluggableButtonMorph on: `@.arg1 getState: `@.arg2 action: > `@.arg3' do: [ :node :answer | node ]; > yourself > > Of course, if you put all your constructor methods into a distinct > protocol, you could automate the creation of the searcher. > > Lukas > > On 15 January 2012 17:28, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: >> Hi: >> >> When refactoring code, I frequently try to find all places where a class is instantiated. >> Is there anything in the image which would work a bit more precise than a search for the class name in the finder? >> >> Thanks >> Stefan >> >> >> -- >> Stefan Marr >> Software Languages Lab >> Vrije Universiteit Brussel >> Pleinlaan 2 / B-1050 Brussels / Belgium >> http://soft.vub.ac.be/~smarr >> Phone: +32 2 629 2974 >> Fax: +32 2 629 3525 >> >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch >

Jan. 15, 2012

Re: [Pharo-project] Speeding up Finder string search

by Benjamin

Thanks for having a look at this problem. With Camillo, we though about using parallel processes but never go further than an idea :) Ben On Jan 15, 2012, at 6:11 PM, Stefan Marr wrote: > Hi: > > The finder is annoyingly slow when doing string searches. > Compared to a 'grep' its multiple magnitudes slower, at least from my perception :( > > Profiling pointed my at RemoteString>>string and its use of readOnlyCopy on the SourceFiles. > > I put a cache of these read only files into ExpandedSourceFileArray and get a nice speedup. > > { [ Finder new constructSourceDictionary ] timeToRun. > [ Finder new constructSourceDictionary ] timeToRun. > [ Finder new constructSourceDictionary ] timeToRun . } > > Without Cache: #(32079 29034 32274) > With Cache: #(10757 10718 11050) > > > While that works for the searching, it does fall apart for other uses of RemoteString>>string. (For instance, filing out the changes...) > > > If anyone has an idea how to avoid the overhead of copying, I would be all ears. > > > Thanks > Stefan > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: +32 2 629 3525 > >

Jan. 15, 2012

[Pharo-project] [COTDC] 105 - ZipConstants

by sean＠clipperadams.com

104 classes done 793 classes remaining Continuing in Compression... Today: ZipConstants Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest p.s. this message was sent from a pharo image. Did you know you could easily do that?!

Jan. 15, 2012

Re: [Pharo-project] executing a script in headless mode?

by Camillo Bruni

Update, we fixed the issue :) http://code.google.com/p/pharo/issues/detail?id=5175 best cami On 2012-01-14, at 22:29, Bernardo Ezequiel Contreras wrote: > i try it again with the last image #14283 and it doesn't work > > On Sat, Jan 14, 2012 at 4:12 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 14 Jan 2012, at 19:28, Bernardo Ezequiel Contreras wrote: > > > file://home/vonbecmann/pharo-projects/trunk/set-up.st > > /home/vonbecmann/pharo-projects/trunk/set-up.st should work just as well. > > > >

Jan. 15, 2012

[Pharo-project] Speeding up Finder string search

by Stefan Marr

Hi: The finder is annoyingly slow when doing string searches. Compared to a 'grep' its multiple magnitudes slower, at least from my perception :( Profiling pointed my at RemoteString>>string and its use of readOnlyCopy on the SourceFiles. I put a cache of these read only files into ExpandedSourceFileArray and get a nice speedup. { [ Finder new constructSourceDictionary ] timeToRun. [ Finder new constructSourceDictionary ] timeToRun. [ Finder new constructSourceDictionary ] timeToRun . } Without Cache: #(32079 29034 32274) With Cache: #(10757 10718 11050) While that works for the searching, it does fall apart for other uses of RemoteString>>string. (For instance, filing out the changes...) If anyone has an idea how to avoid the overhead of copying, I would be all ears. Thanks Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Jan. 15, 2012

Re: [Pharo-project] Bug in pharo image

by Garret Raziel

Ok, I will open the bug. I didn't mean it bad, I just only wanted to know if it isn't inappropriate to post about bug in mailinglist. Jan

Jan. 15, 2012

Re: [Pharo-project] Finding all places where a class is instantiated?

by Stefan Marr

Hi Lukas: On 15 Jan 2012, at 17:46, Lukas Renggli wrote: > Depends on how you use your classes. > > If you have have a finite set of constructor methods you can use > 'Refactor > Search code...' with something like this: > > RBParseTreeSearcher new > matches: 'PluggableButtonMorph on: `@.arg1' do: [ :node :answer | node ]; > matches: 'PluggableButtonMorph on: `@.arg1 getState: `@.arg2 action: > `@.arg3' do: [ :node :answer | node ]; > yourself > Of course, if you put all your constructor methods into a distinct > protocol, you could automate the creation of the searcher. Hm, I should probably find out how to use that. But the code is old and not properly categorized, and all in all also not large enough to really worry. It is just one of those Sundays where these kind of little things are annoying ;) Thanks Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Jan. 15, 2012

Re: [Pharo-project] Finding all places where a class is instantiated?

by Lukas Renggli

Depends on how you use your classes. If you have have a finite set of constructor methods you can use 'Refactor > Search code...' with something like this: RBParseTreeSearcher new matches: 'PluggableButtonMorph on: `@.arg1' do: [ :node :answer | node ]; matches: 'PluggableButtonMorph on: `@.arg1 getState: `@.arg2 action: `@.arg3' do: [ :node :answer | node ]; yourself Of course, if you put all your constructor methods into a distinct protocol, you could automate the creation of the searcher. Lukas On 15 January 2012 17:28, Stefan Marr <smalltalk(a)stefan-marr.de> wrote: > Hi: > > When refactoring code, I frequently try to find all places where a class is instantiated. > Is there anything in the image which would work a bit more precise than a search for the class name in the finder? > > Thanks > Stefan > > > -- > Stefan Marr > Software Languages Lab > Vrije Universiteit Brussel > Pleinlaan 2 / B-1050 Brussels / Belgium > http://soft.vub.ac.be/~smarr > Phone: +32 2 629 2974 > Fax: Â +32 2 629 3525 > > -- Lukas Renggli www.lukas-renggli.ch

Jan. 15, 2012