November 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] about name for logging message

by StÃ©phane Ducasse

In 14217 there is no TranscriptModel (I thought that we removed it from 1.3 too). There is just ThreadSafeTranscript and no log: method there and it uses a Mutex too. So what I suggest is that if you want that we update the 1.3 version provide code that we can just load. LIke that we will integrate it in the next batch. Right now I'm trying to clean the back log of issues in 1.4 Stef > > On 05 Nov 2011, at 22:37, StÃ©phane Ducasse wrote: >> >> AddEntry: is a low level api. >> Now I will check because there were some movements around transcript in 1.3 and may be some left over were not cleaned. > > Ok, thanks, did not see the #log: the first time I looked at the class. > > > Is probably already fixed, but in my #13281 image, TranscriptModel is not threadsafe. It seem to try to be threadsafe, but there is a problem when multiple processes do #log: and get interleaved while updating/redrawing the display. > > In my image, I just replaced the Semaphore with a Mutex (which is reentrant) and put a critical section in #log: > > 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 > >

Nov. 6, 2011

Re: [Pharo-project] about name for logging message

by StÃ©phane Ducasse

can you publish the code and I will fill a bug entry. May be log: was added after. On Nov 6, 2011, at 3:15 AM, Stefan Marr wrote: > > On 05 Nov 2011, at 22:37, StÃ©phane Ducasse wrote: >> >> AddEntry: is a low level api. >> Now I will check because there were some movements around transcript in 1.3 and may be some left over were not cleaned. > > Ok, thanks, did not see the #log: the first time I looked at the class. > > > Is probably already fixed, but in my #13281 image, TranscriptModel is not threadsafe. It seem to try to be threadsafe, but there is a problem when multiple processes do #log: and get interleaved while updating/redrawing the display. > > In my image, I just replaced the Semaphore with a Mutex (which is reentrant) and put a critical section in #log: > > 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 > >

Nov. 6, 2011

[Pharo-project] Funny DrGeo sketch

by Hilaire Fernandes

http://blog.ofset.org/hilaire/index.php?post/2011/10/28/Huge-sketch

Nov. 6, 2011

Re: [Pharo-project] Headless PetitParser

by Lukas Renggli

Alberto, Have a look at the how TextLint (a PetitParser thingy that creates some output) is integrated into TextMate, Emacs, Vim, ... https://github.com/DamienCassou/textlint The Pharo VM is started through some (shell) scripts that are called by the respective editors (but these scripts also work independently): Emacs: https://github.com/DamienCassou/textlint/blob/master/textlint.bash TextMate: https://github.com/DamienCassou/textlint/blob/master/TextLint.tmbundle/Comm… Lukas On 6 November 2011 01:04, Stefan Marr <pharo(a)stefan-marr.de> wrote: > Hi Alberto: > > > On 05 Nov 2011, at 23:29, Alberto Bacchelli wrote: > >> ./myParser -i fileToParse.txt -o outputFile.txt >> >> Is there any possibility to do that? Can a headless Pharo be a >> solution? If so, how can I start and use a headless Pharo? Is there >> any useful documentation/email about it? > > > > > I attached the stuff I currently use. > There might be better ways to do it, but the attached code is Squeak 3.9 and Pharo 1.3 compatible... > > [There might be bugs with regard to saving images and restarting etc. > Have not checked whether that is the latest version of the code. > But should be good enough to get an idea, and might be sufficient for your use case.] > > The HelloWorld class should get you started. > > On OSX you would need a fairly new VM, I think. The old ones did not play nice with the command-line. > > The hello world should look like this: > > $ your-vm-binary -headless your.image HelloWorld foo bar baz > > > > > 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 > > > -- Lukas Renggli www.lukas-renggli.ch

Nov. 6, 2011

Re: [Pharo-project] crash of the vm on ubuntu

by Lukas Renggli

Yes, seems to work quite stable. Only with Eliot's VM though, not with any of the official Pharo VMs. Maybe consider updating them? Lukas On 4 November 2011 16:22, Jorge Ressia <jorge.ressia(a)gmail.com> wrote: > Hi guys, > > Flushing the selector is enough. > > Eliot fixed this problem some time ago. Look at the discussion > http://forum.world.st/Re-Pharo-project-Troubles-with-flushCache-and-run-wit… > > @Alex I have a test case that I built for Eliot. If you send me your image > and VM I can try out to see if there is a similar problem. > > Cheers, > > > On Fri, Nov 4, 2011 at 3:31 PM, Mariano Martinez Peck > <marianopeck(a)gmail.com> wrote: >> >> Flushing the behavior is way too much, since if I understand correctly, it >> will flush the whole method cache (including PICs etc ). >> In my experience, with the latest version, just flushing the selector is >> enough. It is not in your case? >> >> Cheers >> >> On Fri, Nov 4, 2011 at 3:18 PM, Alexandre Bergel <alexandre.bergel(a)me.com> >> wrote: >>> >>> > What is still not clear to me is what you need to flush when replacing >>> > a method with an object. The selector, the old method, the new method, or >>> > the behavior? Last time I tried I got the best results flushing the >>> > behavior, but I would like to know what should be used for real. >>> >>> +1 >>> I also flush the behavior. >>> >>> Alexandre >>> >>> > >>> > On Friday, 4 November 2011, Alexandre Bergel <alexandre.bergel(a)me.com> >>> > wrote: >>> > > Ok >>> > > Thanks, we will try >>> > > >>> > > Alexandre >>> > > >>> > > >>> > > On 4 Nov 2011, at 11:01, Mariano Martinez Peck wrote: >>> > > >>> > >> >>> > >> >>> > >> On Fri, Nov 4, 2011 at 2:14 PM, Alexandre Bergel >>> > >> <alexandre.bergel(a)me.com> wrote: >>> > >> Hi! >>> > >> >>> > >> My students are experiencing frequent crashes of the CogVM when >>> > >> playing with Spy (a profiling framework that instrument compile methods and >>> > >> replace them during the execution). My students use a MooseOneClick bundle. >>> > >> I am not sure which version of the CogVM they use actually. Is there a way >>> > >> to check this? >>> > >> >>> > >> Anyone has experienced frequent crashes with Ubuntu? >>> > >> >>> > >> There were some issues with #cannotInterpret: and #run:with:in Â with >>> > >> previous versions of Cog. However, with the last version Eliot' Cog all of >>> > >> them are fixed >>> > >> >>> > >> >>> > >> Cheers, >>> > >> Alexandre >>> > >> -- >>> > >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> > >> Alexandre Bergel Â http://www.bergel.eu >>> > >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> -- >>> > >> Mariano >>> > >> http://marianopeck.wordpress.com >>> > >> >>> > > >>> > > -- >>> > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> > > Alexandre Bergel Â http://www.bergel.eu >>> > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > >>> > -- >>> > Lukas Renggli >>> > www.lukas-renggli.ch >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel Â http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > > -- > Jorge Ressia > www.jorgeressia.com > -- Lukas Renggli www.lukas-renggli.ch

Nov. 6, 2011

Re: [Pharo-project] about name for logging message

by Stefan Marr

On 05 Nov 2011, at 22:37, StÃ©phane Ducasse wrote: > > AddEntry: is a low level api. > Now I will check because there were some movements around transcript in 1.3 and may be some left over were not cleaned. Ok, thanks, did not see the #log: the first time I looked at the class. Is probably already fixed, but in my #13281 image, TranscriptModel is not threadsafe. It seem to try to be threadsafe, but there is a problem when multiple processes do #log: and get interleaved while updating/redrawing the display. In my image, I just replaced the Semaphore with a Mutex (which is reentrant) and put a critical section in #log: 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

Nov. 6, 2011

Re: [Pharo-project] Headless PetitParser

by Stefan Marr

Hi Alberto: On 05 Nov 2011, at 23:29, Alberto Bacchelli wrote: > ./myParser -i fileToParse.txt -o outputFile.txt > > Is there any possibility to do that? Can a headless Pharo be a > solution? If so, how can I start and use a headless Pharo? Is there > any useful documentation/email about it? I attached the stuff I currently use. There might be better ways to do it, but the attached code is Squeak 3.9 and Pharo 1.3 compatible... [There might be bugs with regard to saving images and restarting etc. Have not checked whether that is the latest version of the code. But should be good enough to get an idea, and might be sufficient for your use case.] The HelloWorld class should get you started. On OSX you would need a fairly new VM, I think. The old ones did not play nice with the command-line. The hello world should look like this: $ your-vm-binary -headless your.image HelloWorld foo bar baz 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

Nov. 6, 2011

Re: [Pharo-project] Headless PetitParser

by Fabrizio Perin

Hi alberto, i'm not sure about the solution of your problem although i would try to prepare a simple st script were you basically say to the parser which file to parse and simply flush on a file the output of the parser. Than you can start an headless image passing the st file as input. Hope this will help. Cheers, Fabrizio 2011/11/5 Alberto Bacchelli <alberto.bacchelli(a)usi.ch> > Hi all, > > I have a small parser written in PetitParser ;) I would like to call > it from a non Smalltalk application (e.g., Java, javascript) or, more > generally, from a Unix command line. > I was thinking about something like: > > ./myParser -i fileToParse.txt -o outputFile.txt > > Is there any possibility to do that? Can a headless Pharo be a > solution? If so, how can I start and use a headless Pharo? Is there > any useful documentation/email about it? > > Thank you a lot for any help. > > Cheers, > Alberto > >

Nov. 5, 2011

Re: [Pharo-project] about name for logging message

by Guillermo Polito

I like #trace: :). Other I do not like so should be #record: or #writeDown: (ugly, hehe) :P Why not just #newLine instead of #nl :(? Therer are 5 more characters but I'm happier :P... On Sat, Nov 5, 2011 at 6:37 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Hi stefan > > > > >> self log: > >> self logCr: > > > > Why is it a rather platform specific CR? Why not some platform > independent NL (new line)? > > > Indeed nl is better. I used Cr because people with > Transcript show: 'foo' ; cr and not nl as far as I know > > > And in 1.3, I found the TranscriptModel with #addEntry: which looked > like the new way of doing things since #show: has some comment which said > it is deprecated/or not cool anymore. > > AddEntry: is a low level api. > Now I will check because there were some movements around transcript in > 1.3 and may be some left over were not cleaned. > > > > > > 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 > > > > > > >

Nov. 5, 2011

[Pharo-project] Headless PetitParser

by Alberto Bacchelli

Hi all, I have a small parser written in PetitParser ;) I would like to call it from a non Smalltalk application (e.g., Java, javascript) or, more generally, from a Unix command line. I was thinking about something like: ./myParser -i fileToParse.txt -o outputFile.txt Is there any possibility to do that? Can a headless Pharo be a solution? If so, how can I start and use a headless Pharo? Is there any useful documentation/email about it? Thank you a lot for any help. Cheers, Alberto

Nov. 5, 2011