July 2020 - Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #560: ReUtilityMethodsRule-speedup-and-test

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #560 was: FAILURE. The Pull Request #6967 was integrated: "ReUtilityMethodsRule-speedup-and-test" Pull request url: https://github.com/pharo-project/pharo/pull/6967 Issue Url: https://github.com/pharo-project/pharo/issues/ReUtilityMethodsRule Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 29, 2020

Re: [Pharo-dev] [rmod] scripting pharo How to disable settings loading..

by StÃ©phane Ducasse

Thanks cyril I found it by removing my settings. Now to me this means that the settings should be managed after the handlers. S. > On 29 Jul 2020, at 19:06, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Hi, > > You need to add `--no-default-preferences` after the image name. > > pharo80 /Users/ducasse/Documents/Pharo/images/P8Indian/P8Indian.image > --no-default-preferences --list > > On Wed, Jul 29, 2020 at 6:57 PM StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> Hi >> >> I would like to write some scripts with Pharo. >> Now I cannot find how to block the settings >> because I have a crash in my settings >> >> >> pharo80 /Users/ducasse/Documents/Pharo/images/P8Indian/P8Indian.image --list >> pharo80 /Users/ducasse/Documents/Pharo/images/P8Indian/P8Indian.image â-help >> pharo80 /Users/ducasse/Documents/Pharo/images/P8Indian/P8Indian.image -help >> >> All of them crash because my settings are broken >> >> >> >> doing the following does not help >> >> pharo80 --help >> Usage: /Users/ducasse/bin/Pharo/Pharo64Stable.app/Contents/MacOS/Pharo [<option>...] [<imageName> [<argument>...]] >> /Users/ducasse/bin/Pharo/Pharo64Stable.app/Contents/MacOS/Pharo [<option>...] -- [<argument>...] >> >> Common <option>s: >> --help print this help message, then exit >> --memory <size>[mk] use fixed heap size (added to image size) >> --nohandlers disable sigsegv & sigusr1 handlers >> --timephases print start load and run times >> --breaksel selector set breakpoint on send of selector >> --breakmnu selector set breakpoint on MNU of selector >> --eden <size>[mk] set eden memory to bytes >> --leakcheck num check for leaks in the heap >> --stackpages num use n stack pages >> --numextsems num make the external semaphore table num in size >> --noheartbeat disable the heartbeat for VM debugging. disables input >> --pollpip output . on each poll for input >> --checkpluginwrites check for writes past end of object in plugins >> --trace[=num] enable tracing (optionally to a specific value) >> --warnpid print pid in warnings >> --codesize <size>[mk] set machine code memory to bytes >> --tracestores enable store tracing (assert check stores) >> --cogmaxlits <n> set max number of literals for methods to be compiled to machine code >> --cogminjumps <n> set min number of backward jumps for interpreted methods to be considered for compilation to machine code >> --reportheadroom report unused stack headroom on exit >> --maxoldspace <size>[mk] set max size of old space memory to bytes >> --logscavenge log scavenging to scavenge.log >> --headless run in headless (no window) mode (default: false) >> --headfull run in headful (window) mode (default: true) >> --version print version information, then exit >> --blockonerror on error or segv block, not exit. useful for attaching gdb >> --blockonwarn on warning block, don't warn. useful for attaching gdb >> --exitonwarn treat warnings as errors, exiting on warn >> >> Notes: >> <imageName> defaults to `Pharo.image'. >> If '--memory' or '-maxoldspace' are not specified then the heap will grow dynamically. >> <argument>s are ignored, but are processed by the Squeak image. >> The first <argument> normally names a Squeak `script' to execute. >> Precede <arguments> by `--' to use default image. >> >> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Aurore Dalle >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> > > > -- > Cyril Ferlicot > https://ferlicot.fr -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

July 29, 2020

Re: [Pharo-dev] [GemStone-Smalltalk] [squeak-dev] Webminar about VA Smalltalk new OS Process Framework

by Mariano Martinez Peck

Hi, This webinar already took place but you can see the recording here: https://youtu.be/uwEu_-tflKg Best, On Wed, Jul 29, 2020 at 12:57 PM Norman Nunley via GemStone-Smalltalk < gemstone-smalltalk(a)lists.gemtalksystems.com> wrote: > Is there any chance that you'll record this webinar? I'd love to attend, > but I have work meeting conflicts. > > Norman > > On Wed, Jul 8, 2020 at 10:36 AM Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> Greetings all, This is a friendly reminder of the presentation we will >> host tomorrow for VAST's newest OSProcess framework. Best regards, >> >> On Tue, Jun 30, 2020 at 10:25 AM Mariano Martinez Peck < >> marianopeck(a)gmail.com> wrote: >> >>> Greetings all, >>> >>> Some time ago, I had the pleasure and privilege of being sponsored by >>> the Pharo Consortium to implement OSSubprocess. Because of that work, I >>> quickly realized that a new OS process framework created by Instantiations >>> was quite advanced and unlike anything I had seen before. If you are able, >>> I would highly recommend that you attend the technology preview of this >>> framework coming to VAST 2021: >>> >>> Seth Berman will be presenting, registration here: >>> https://attendee.gotowebinar.com/register/7491754880594201356 >>> >>> We hope the community can attend and we look forward to your feedback >>> and questions during the event's Q&A session. >>> >>> Best regards, >>> >>> -- >>> Mariano Martinez Peck >>> Email: marianopeck(a)gmail.com >>> Twitter: @MartinezPeck >>> LinkedIn: www.linkedin.com/in/mariano-martinez-peck >>> <https://www.linkedin.com/in/mariano-mart%C3%ADnez-peck/> >>> Blog: https://marianopeck.wordpress.com/ >>> >> >> >> -- >> Mariano Martinez Peck >> Email: marianopeck(a)gmail.com >> Twitter: @MartinezPeck >> LinkedIn: www.linkedin.com/in/mariano-martinez-peck >> <https://www.linkedin.com/in/mariano-mart%C3%ADnez-peck/> >> Blog: https://marianopeck.wordpress.com/ >> >> _______________________________________________ > GemStone-Smalltalk mailing list > GemStone-Smalltalk(a)lists.gemtalksystems.com > https://lists.gemtalksystems.com/mailman/listinfo/gemstone-smalltalk > -- Mariano Martinez Peck Email: marianopeck(a)gmail.com Twitter: @MartinezPeck LinkedIn: www.linkedin.com/in/mariano-martinez-peck <https://www.linkedin.com/in/mariano-mart%C3%ADnez-peck/> Blog: https://marianopeck.wordpress.com/

July 29, 2020

Re: [Pharo-dev] [rmod] scripting pharo How to disable settings loading..

by Cyril Ferlicot

Hi, You need to add `--no-default-preferences` after the image name. pharo80 /Users/ducasse/Documents/Pharo/images/P8Indian/P8Indian.image --no-default-preferences --list On Wed, Jul 29, 2020 at 6:57 PM StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > Hi > > I would like to write some scripts with Pharo. > Now I cannot find how to block the settings > because I have a crash in my settings > > > pharo80 /Users/ducasse/Documents/Pharo/images/P8Indian/P8Indian.image --list > pharo80 /Users/ducasse/Documents/Pharo/images/P8Indian/P8Indian.image â-help > pharo80 /Users/ducasse/Documents/Pharo/images/P8Indian/P8Indian.image -help > > All of them crash because my settings are broken > > > > doing the following does not help > > pharo80 --help > Usage: /Users/ducasse/bin/Pharo/Pharo64Stable.app/Contents/MacOS/Pharo [<option>...] [<imageName> [<argument>...]] > /Users/ducasse/bin/Pharo/Pharo64Stable.app/Contents/MacOS/Pharo [<option>...] -- [<argument>...] > > Common <option>s: > --help print this help message, then exit > --memory <size>[mk] use fixed heap size (added to image size) > --nohandlers disable sigsegv & sigusr1 handlers > --timephases print start load and run times > --breaksel selector set breakpoint on send of selector > --breakmnu selector set breakpoint on MNU of selector > --eden <size>[mk] set eden memory to bytes > --leakcheck num check for leaks in the heap > --stackpages num use n stack pages > --numextsems num make the external semaphore table num in size > --noheartbeat disable the heartbeat for VM debugging. disables input > --pollpip output . on each poll for input > --checkpluginwrites check for writes past end of object in plugins > --trace[=num] enable tracing (optionally to a specific value) > --warnpid print pid in warnings > --codesize <size>[mk] set machine code memory to bytes > --tracestores enable store tracing (assert check stores) > --cogmaxlits <n> set max number of literals for methods to be compiled to machine code > --cogminjumps <n> set min number of backward jumps for interpreted methods to be considered for compilation to machine code > --reportheadroom report unused stack headroom on exit > --maxoldspace <size>[mk] set max size of old space memory to bytes > --logscavenge log scavenging to scavenge.log > --headless run in headless (no window) mode (default: false) > --headfull run in headful (window) mode (default: true) > --version print version information, then exit > --blockonerror on error or segv block, not exit. useful for attaching gdb > --blockonwarn on warning block, don't warn. useful for attaching gdb > --exitonwarn treat warnings as errors, exiting on warn > > Notes: > <imageName> defaults to `Pharo.image'. > If '--memory' or '-maxoldspace' are not specified then the heap will grow dynamically. > <argument>s are ignored, but are processed by the Squeak image. > The first <argument> normally names a Squeak `script' to execute. > Precede <arguments> by `--' to use default image. > > > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Aurore Dalle > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > -- Cyril Ferlicot https://ferlicot.fr

July 29, 2020

scripting pharo How to disable settings loading..

by StÃ©phane Ducasse

Hi I would like to write some scripts with Pharo. Now I cannot find how to block the settings because I have a crash in my settings pharo80 /Users/ducasse/Documents/Pharo/images/P8Indian/P8Indian.image --list pharo80 /Users/ducasse/Documents/Pharo/images/P8Indian/P8Indian.image â-help pharo80 /Users/ducasse/Documents/Pharo/images/P8Indian/P8Indian.image -help All of them crash because my settings are broken doing the following does not help pharo80 --help Usage: /Users/ducasse/bin/Pharo/Pharo64Stable.app/Contents/MacOS/Pharo [<option>...] [<imageName> [<argument>...]] /Users/ducasse/bin/Pharo/Pharo64Stable.app/Contents/MacOS/Pharo [<option>...] -- [<argument>...] Common <option>s: --help print this help message, then exit --memory <size>[mk] use fixed heap size (added to image size) --nohandlers disable sigsegv & sigusr1 handlers --timephases print start load and run times --breaksel selector set breakpoint on send of selector --breakmnu selector set breakpoint on MNU of selector --eden <size>[mk] set eden memory to bytes --leakcheck num check for leaks in the heap --stackpages num use n stack pages --numextsems num make the external semaphore table num in size --noheartbeat disable the heartbeat for VM debugging. disables input --pollpip output . on each poll for input --checkpluginwrites check for writes past end of object in plugins --trace[=num] enable tracing (optionally to a specific value) --warnpid print pid in warnings --codesize <size>[mk] set machine code memory to bytes --tracestores enable store tracing (assert check stores) --cogmaxlits <n> set max number of literals for methods to be compiled to machine code --cogminjumps <n> set min number of backward jumps for interpreted methods to be considered for compilation to machine code --reportheadroom report unused stack headroom on exit --maxoldspace <size>[mk] set max size of old space memory to bytes --logscavenge log scavenging to scavenge.log --headless run in headless (no window) mode (default: false) --headfull run in headful (window) mode (default: true) --version print version information, then exit --blockonerror on error or segv block, not exit. useful for attaching gdb --blockonwarn on warning block, don't warn. useful for attaching gdb --exitonwarn treat warnings as errors, exiting on warn Notes: <imageName> defaults to `Pharo.image'. If '--memory' or '-maxoldspace' are not specified then the heap will grow dynamically. <argument>s are ignored, but are processed by the Squeak image. The first <argument> normally names a Squeak `script' to execute. Precede <arguments> by `--' to use default image. -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

July 29, 2020

[Pharo 9.0] Build #559: merge-spec2-0.7.2

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #559 was: FAILURE. The Pull Request #7002 was integrated: "merge-spec2-0.7.2" Pull request url: https://github.com/pharo-project/pharo/pull/7002 Issue Url: https://github.com/pharo-project/pharo/issues/merge Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 29, 2020

Re: [Pharo-dev] Microdown ?

by Sean P. DeNigris

NorbertHartl wrote > Microdown is a subset of markdown that can parse to a pillar model. So the > discussions about pillar markup have finally settled and we have a syntax > format that reads well in ascii which can be used in class comments even > if it is a basic image. Rich text comments are an exciting development! I'd like to understand the benefit of Microdown vs. full Pillar syntax. Presumably the primary benefit is the size of the codebase. Any other reasons? Generally, I wonder about minimalism when it applies to areas of the system that seem inherently non-minimalist e.g. test harnesses, documentation, etc. I though a lot about this when trying to document and refactor SDL. The lack of a mock library in core was a big barrier to understanding the interactions between SDL objects. Maybe I'm being naive, but I feel like if someone wants a minimal image, they're not going to want to load SUnit or rich text documentation *at all*, so I don't see the risk-benefit of crippling these features. A few other questions about the "rich text doc" roadmap: 1. Could/will this be extended to method comments? That would be really cool :) 2. How close are we for someone to use full Pillar syntax in class comments in their own library? Any plans to make this possible? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

July 28, 2020

Re: [Pharo-dev] Microdown ?

by Sean P. DeNigris

Pharo Smalltalk Developers mailing list wrote > With MicroPrint, you can do this: Was that a typo, or is there another library called "MicroPrint"?! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

July 28, 2020

[Pharo 9.0] Build #558: RBLintRule-enabledSettingID

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #558 was: SUCCESS. The Pull Request #7000 was integrated: "RBLintRule-enabledSettingID" Pull request url: https://github.com/pharo-project/pharo/pull/7000 Issue Url: https://github.com/pharo-project/pharo/issues/RBLintRule Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 28, 2020

[Pharo 9.0] Build #557: Reduce-References-RBVariableNode-subclasses2

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #557 was: FAILURE. The Pull Request #6990 was integrated: "Reduce-References-RBVariableNode-subclasses2" Pull request url: https://github.com/pharo-project/pharo/pull/6990 Issue Url: https://github.com/pharo-project/pharo/issues/Reduce Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 28, 2020