- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo-users] including Pillar in Pharo image by default

by Esteban Lorenzano

> On 12 Aug 2017, at 18:22, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Esteban, I think that when Stef says "a mini version of pillar" he does not mean a mini version of the parser or the AST, but a version that does not have the exporting to html/latex/â¦ I know that. But Cyril talked about âgetting a parser without PPâ. That's where my comment belongs :) Esteban > > On Sat, Aug 12, 2017 at 4:37 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > and btw, this kind of threads belongs to pharo-dev, not to pharo-users :) > > Esteban > > > On 12 Aug 2017, at 16:35, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > > > > > >> On 12 Aug 2017, at 12:46, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: > >> > >> Hi, > >> > >> I would very much like this path. What would constitute tiny? > > > > no idea, we need to think on it :) > > but I see no point in create a new (even small) parser/scanner each time we need one. At the end you have several small parsers that repeat always same process when PetitParser is good for most of our problems (and if you need to improve it. you can always load PP compiler, etc.). > > > > Esteban > > > >> > >> Cheers, > >> Doru > >> > >> > >>> On Aug 11, 2017, at 9:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > >>> > >>> hi, > >>> > >>>> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote: > >>>> > >>>> Another step would be to get a minimal parser not relying on > >>>> PetitParser. > >>> > >>> Letâs think differently: why not to include a tiny PetitParser? > >>> Then we can think on: > >>> > >>> - pillar sintax (better than just a restricted version) > >>> - simplify other âsmall parsersâ that are already on the image. > >>> - we provide a tool to o cool stuff (instead relying as always in regexp, etc.) > >>> > >>> cheers, > >>> Esteban > >> > >> -- > >> www.tudorgirba.com <http://www.tudorgirba.com/> > >> www.feenk.com <http://www.feenk.com/> > >> > >> "Beauty is where we see it." > >> > >> > >> > >> > >> > > > > > > > > -- > > Guille Polito > > Research Engineer > French National Center for Scientific Research - http://www.cnrs.fr <http://www.cnrs.fr/> > > > Web: http://guillep.github.io <http://guillep.github.io/> > Phone: +33 06 52 70 66 13

Aug. 12, 2017

Re: [Pharo-dev] [Pharo-users] including Pillar in Pharo image by default

by Guillermo Polito

Esteban, I think that when Stef says "a mini version of pillar" he does not mean a mini version of the parser or the AST, but a version that does not have the exporting to html/latex/... On Sat, Aug 12, 2017 at 4:37 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > and btw, this kind of threads belongs to pharo-dev, not to pharo-users :) > > Esteban > > > On 12 Aug 2017, at 16:35, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > > >> On 12 Aug 2017, at 12:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> > >> Hi, > >> > >> I would very much like this path. What would constitute tiny? > > > > no idea, we need to think on it :) > > but I see no point in create a new (even small) parser/scanner each time > we need one. At the end you have several small parsers that repeat always > same process when PetitParser is good for most of our problems (and if you > need to improve it. you can always load PP compiler, etc.). > > > > Esteban > > > >> > >> Cheers, > >> Doru > >> > >> > >>> On Aug 11, 2017, at 9:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >>> > >>> hi, > >>> > >>>> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> > wrote: > >>>> > >>>> Another step would be to get a minimal parser not relying on > >>>> PetitParser. > >>> > >>> Letâs think differently: why not to include a tiny PetitParser? > >>> Then we can think on: > >>> > >>> - pillar sintax (better than just a restricted version) > >>> - simplify other âsmall parsersâ that are already on the image. > >>> - we provide a tool to o cool stuff (instead relying as always in > regexp, etc.) > >>> > >>> cheers, > >>> Esteban > >> > >> -- > >> www.tudorgirba.com > >> www.feenk.com > >> > >> "Beauty is where we see it." > >> > >> > >> > >> > >> > > > > > -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 12, 2017

Re: [Pharo-dev] [Pharo-users] including Pillar in Pharo image by default

by Esteban Lorenzano

and btw, this kind of threads belongs to pharo-dev, not to pharo-users :) Esteban > On 12 Aug 2017, at 16:35, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 12 Aug 2017, at 12:46, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> I would very much like this path. What would constitute tiny? > > no idea, we need to think on it :) > but I see no point in create a new (even small) parser/scanner each time we need one. At the end you have several small parsers that repeat always same process when PetitParser is good for most of our problems (and if you need to improve it. you can always load PP compiler, etc.). > > Esteban > >> >> Cheers, >> Doru >> >> >>> On Aug 11, 2017, at 9:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> hi, >>> >>>> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com> wrote: >>>> >>>> Another step would be to get a minimal parser not relying on >>>> PetitParser. >>> >>> Letâs think differently: why not to include a tiny PetitParser? >>> Then we can think on: >>> >>> - pillar sintax (better than just a restricted version) >>> - simplify other âsmall parsersâ that are already on the image. >>> - we provide a tool to o cool stuff (instead relying as always in regexp, etc.) >>> >>> cheers, >>> Esteban >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Beauty is where we see it." >> >> >> >> >> >

Aug. 12, 2017

Re: [Pharo-dev] New line on command line

by Rajula Vineet

    Hi Rajula Hey     On Sat, Aug 12, 2017 at 12:56 AM, Rajula Vineet <[hidden email]> wrote:         Hey,         I have been trying to print on the command line as a part of my handler         implementation. I have been using `nextPutAll: aString;lf.` Apparently, 'lf'         does not seem to work. I tried 'cr' too. I am using the latest 7.0 Pharo-vm         and pharo image. I tried 'OSPlatform current lineEnding' as suggested by         Clement Mastin. But, when I used the 6.0 version the 'lf' message is working         fine.     We did some changes to remodularize a bit more the kernel some weeks ago.     The correct way to print a line ending is, as Clement pointed out, 'OSPlatform current lineEnding'. That is because there is no portable character for a new line. Each platform has its own. Oh! Cool!     That said, maybe you found a bug :). Since the image before automatically transformed cr's in line endings for a platform, I did a stream decorator that replaces that behaviour for Pharo 7, I just did it to make it work, did not test it further actually. Oh! Yeah, it might be a bug.     Could you try the following?      - seeing what happens if you print a new line twice?           nextPutAll: aString; lf;lf I tried it out, it is not changing anything. No new line.       - What is the stream you're using to print out? Transcript or Stdout? Could you show the entire expression you're using? Yeah, I am using stdout. This is the expression self stdoutnextPutAll: (SystemVersion current highestUpdate) asString;lf.       - Can you print out the stream you're using?          stream nextPutAll: stream asString; lf. Yeah, the stream I am using is a VTermOutputDriver.     Guille       Rajula         Please find the attached image which demonstrates the same. The left         terminal is of version 7.0, right one is of 6.0. Can someone help me out         with this?         <http://forum.world.st/file/n4960327/Screenshot_from_2017-08-11_00-04-29.png>         --         View this message in context: http://forum.world.st/New-line-on-command-line-tp4960327.html         Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.     --                    Guille Polito     Research Engineer     French National Center for Scientific Research - http://www.cnrs.fr     Web: http://guillep.github.io     Phone: +33 06 52 70 66 13   -- View this message in context: http://forum.world.st/New-line-on-command-line-tp4960327p4960423.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 12, 2017

Re: [Pharo-dev] Launcher Error w Pharo 7

by Sean P. DeNigris

Sean P. DeNigris wrote > Maybe a Launcher bug then? I think I found it. It seems to be a bug in the way Launcher/Pharo unzips the downloaded VM. The symlink libgit2.dylib becomes unlinked and appears as just a regular file. If I delete the Pharo.app and unzip 70.zip (which btw maybe should have been deleted during cleanup after the dl) to ./vms/70, the error disappears! FYI I'm headed to the airport and so will not be able to open an issue for this. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Launcher-Error-w-Pharo-7-tp4959777p4960417.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 12, 2017

Re: [Pharo-dev] Launcher Error w Pharo 7

by Sean P. DeNigris

Tim Mackinnon wrote > Hi Sean - I know that the vm was upgraded due to new feature requirements > of libgit so I'm guessing you don't have the latest vm? Maybe a Launcher bug then? It put up a progess bar while "downloading Pharo 7 VM" (paraphrased). There is now a Pharo VM in ~/Documents/Pharo/vms/70/Pharo.app which has, in the Plugins folder, a libgit2.dylib which points to ./libgit2.0.25.1.dylib, which I also see exists. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Launcher-Error-w-Pharo-7-tp4959777p4960415.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 12, 2017

Re: [Pharo-dev] [Ann] libssh2 binding for Pharo

by Sean P. DeNigris

Max Leske wrote > Very cool! +100. I can think of lots of places where I'd use this. In the past, due to all the flux in FFI (and laziness ha ha), I used some really complicated mechanisms to script Mac Terminal and then capture and parse the output :/ ----- Cheers, Sean -- View this message in context: http://forum.world.st/Ann-libssh2-binding-for-Pharo-tp4959958p4960414.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 12, 2017

Re: [Pharo-dev] Pharo 7 provisional HOWTO

by Pavel Krivanek

2017-08-12 11:36 GMT+02:00 Holger Freyther <holger(a)freyther.de>: > > > On 26. Jun 2017, at 19:14, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > > > Hi, > > Hey! > > thank you for this HOWTO! > > > username := 'YOUR-USER-NAME'. > > repository := IceRepositoryCreator new > > url: 'git@github.com:pharo-project/pharo.git'; > > location: ('pharo-core' asFileReference ensureCreateDirectory); > > subdirectory:'src'; > > createRepository. > > repository checkoutBranch: 'development'. > > repository register. > > > > fork := (IceRemote name: 'myFork' url: ('git@github.com:{1}/pharo.git' > format: {username})). > > repository addRemote: fork. > > repository pushRemote: fork. > > repository pullRemote: repository origin. > > I am using "pharo-mac-stable.zip" and "Pharo-7.0.0-alpha.build.27.sha.c1c8991.arch.32bit.zip" > and followed your howto and run into various Iceberg issues. Where would be > the best place to report them? > > Open Iceberg, selech "Pharo", click on Branches > => Error LGit_GIT_ERROR: Reference 'HEAD' is not a local branch. > > Open Iceberg, double click on "Pharo" > => DNU, #/ was sent to nil > UndefinedObject(Object)>>doesNotUnderstand: #/ > ... IceSavedPackage repository location seems to return nil. > > > Are these known? Fogbugz? Github issues of Iceberg? > yes, because this HOWTO is already obsolete. See: https://github.com/guillep/PharoIntegrationProcess/wiki/Pharo-Development-P… -- Pavel > > > cheers > holger > > > > >

Aug. 12, 2017

Re: [Pharo-dev] Pharo 7 provisional HOWTO

by Holger Freyther

> On 26. Jun 2017, at 19:14, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > Hi, Hey! thank you for this HOWTO! > username := 'YOUR-USER-NAME'. > repository := IceRepositoryCreator new > url: 'git@github.com:pharo-project/pharo.git'; > location: ('pharo-core' asFileReference ensureCreateDirectory); > subdirectory:'src'; > createRepository. > repository checkoutBranch: 'development'. > repository register. > > fork := (IceRemote name: 'myFork' url: ('git@github.com:{1}/pharo.git' format: {username})). > repository addRemote: fork. > repository pushRemote: fork. > repository pullRemote: repository origin. I am using "pharo-mac-stable.zip" and "Pharo-7.0.0-alpha.build.27.sha.c1c8991.arch.32bit.zip" and followed your howto and run into various Iceberg issues. Where would be the best place to report them? Open Iceberg, selech "Pharo", click on Branches => Error LGit_GIT_ERROR: Reference 'HEAD' is not a local branch. Open Iceberg, double click on "Pharo" => DNU, #/ was sent to nil UndefinedObject(Object)>>doesNotUnderstand: #/ ... IceSavedPackage repository location seems to return nil. Are these known? Fogbugz? Github issues of Iceberg? cheers holger

Aug. 12, 2017

Re: [Pharo-dev] [Pharo-users] [ann] moldable brick editor - alpha

by Tudor Girba

Is this still an issue? Could you also try on another OS (just to make sure)? Cheers, Doru > On Aug 10, 2017, at 2:12 PM, stephan <stephan(a)stack.nl> wrote: > > On 10-08-17 13:09, stephan wrote: >> On 05-08-17 00:19, Tudor Girba wrote: >> >Iceberg enableMetacelloIntegration: true. >> That doesn't work. It hangs the image, keeping one CPU >> busy. > > With 60510 that is non-interruptable, b.t.w. > > Stephan > > > > -- www.tudorgirba.com www.feenk.com "Problem solving efficiency grows with the abstractness level of problem understanding."

Aug. 12, 2017