- Pharo-dev - lists.pharo.org

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

Re: [Pharo-project] MAC OS upgrade and Pharo compatibility

by Peter Hugosson-Miller

No, Stef, I'm the same: bugs love me! I am sooooooo glad for the excellent backup program SuperDuper. I did the Lion install two times before it worked OK (third time just like I wrote in my post above), but the other two times I was very happy to have the backup to go back to, I can tell you! -- Cheers, Peter On Sat, Nov 5, 2011 at 10:56 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Yes because I could not update after the first install. > So I was lucky to have another machine where I could install and update > **then** migrate. > I was mad during 3 days. > Of course for everybody around it worked well but I attrack bugs. > Stef > On Nov 5, 2011, at 10:40 PM, Peter Hugosson-Miller wrote: > > > Definitely do a backup, then format the disk and perform a clean > install, then do all the necessary software updates until the machine is > completely up to date. Finally restore your user settings and apps from the > backup. That's my recipe for minimum frustration when dealing with Lion :-) > > > > -- > > Cheers, > > Peter > > > > On Sat, Nov 5, 2011 at 10:34 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > There is no problem for pharo on lion. > > Now do a backup because lion of your machine. > > Lion frustrated me a lot. > > > > And in general when I see the amount of applications spinning to death > on normal usage, I think that pharo is doing well. > > > > Stef > > > > On Nov 5, 2011, at 8:09 PM, Dario Trussardi wrote: > > > > > Hi, > > > > > > i'm interested to upgrade my MacBook Operating System, from > Leopard to Lion version. > > > > > > I'm not expert about it and i will not do error. > > > > > > My question is about Pharo compatibility. > > > > > > Now i work with Pharo 1.0 #10517 and GemTools 1.0-beta.8.3. > > > > > > I need to do something or all work fine after upgrade the O/S ? > > > > > > Thanks, > > > > > > Dario > > > > > > P.S. Excuse me if question is not very very pertinent to Pharo > > > > >

Nov. 5, 2011

Re: [Pharo-project] MAC OS upgrade and Pharo compatibility

by StÃ©phane Ducasse

Yes because I could not update after the first install. So I was lucky to have another machine where I could install and update **then** migrate. I was mad during 3 days. Of course for everybody around it worked well but I attrack bugs. Stef On Nov 5, 2011, at 10:40 PM, Peter Hugosson-Miller wrote: > Definitely do a backup, then format the disk and perform a clean install, then do all the necessary software updates until the machine is completely up to date. Finally restore your user settings and apps from the backup. That's my recipe for minimum frustration when dealing with Lion :-) > > -- > Cheers, > Peter > > On Sat, Nov 5, 2011 at 10:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > There is no problem for pharo on lion. > Now do a backup because lion of your machine. > Lion frustrated me a lot. > > And in general when I see the amount of applications spinning to death on normal usage, I think that pharo is doing well. > > Stef > > On Nov 5, 2011, at 8:09 PM, Dario Trussardi wrote: > > > Hi, > > > > i'm interested to upgrade my MacBook Operating System, from Leopard to Lion version. > > > > I'm not expert about it and i will not do error. > > > > My question is about Pharo compatibility. > > > > Now i work with Pharo 1.0 #10517 and GemTools 1.0-beta.8.3. > > > > I need to do something or all work fine after upgrade the O/S ? > > > > Thanks, > > > > Dario > > > > P.S. Excuse me if question is not very very pertinent to Pharo > >

Nov. 5, 2011

Re: [Pharo-project] MAC OS upgrade and Pharo compatibility

by Peter Hugosson-Miller

Definitely do a backup, then format the disk and perform a clean install, then do all the necessary software updates until the machine is completely up to date. Finally restore your user settings and apps from the backup. That's my recipe for minimum frustration when dealing with Lion :-) -- Cheers, Peter On Sat, Nov 5, 2011 at 10:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > There is no problem for pharo on lion. > Now do a backup because lion of your machine. > Lion frustrated me a lot. > > And in general when I see the amount of applications spinning to death on > normal usage, I think that pharo is doing well. > > Stef > > On Nov 5, 2011, at 8:09 PM, Dario Trussardi wrote: > > > Hi, > > > > i'm interested to upgrade my MacBook Operating System, from > Leopard to Lion version. > > > > I'm not expert about it and i will not do error. > > > > My question is about Pharo compatibility. > > > > Now i work with Pharo 1.0 #10517 and GemTools 1.0-beta.8.3. > > > > I need to do something or all work fine after upgrade the O/S ? > > > > Thanks, > > > > Dario > > > > P.S. Excuse me if question is not very very pertinent to Pharo > > >

Nov. 5, 2011

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

by StÃ©phane Ducasse

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

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

by StÃ©phane Ducasse

Thanks david I do not have OSProcess at hand, but where are these messages defined? On Object? Would it be a problem for you if we define trace and trace: on Object? Stef >>> Hi guys >>> >>> I introduce >>> log to replace Transcript show: ? >>> logCr and crLog >>> >>> Now stupidly I did not notice that it will capture log on number :( and also on collection, >>> >>> So any suggestion of what would be a nice logging message? >>> short and cool. >>> >> How about trace? > > In OSProcess, #trace and #trace: are used for a similar purpose. > This is intended for debugging with "transcript" output coming > from the VM and therefore less dependent on process scheduling > in the image. > > Dave > >

Nov. 5, 2011