August 2018 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Jupyter notebooks / Dynabook / JupyterTalk

by H. Hirzel

Thank you, Evan, for an alternative load script. Unfortunately it gives the same error message. I use a recent, pristine Pharo 6.1 installation on a 64bit Ubuntu based Linux. On 8/4/18, Evan Donahue <emdonahu(a)gmail.com> wrote: > Try: > > Metacello new > githubUser: 'jmari' project: 'JupyterTalk' commitish: 'master' > path: > 'repository'; > baseline: 'JupyterTalk'; > load > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

Aug. 7, 2018

Cargo & Future Proofing Releases

by Evan Donahue

Hi, I will have a few general interest packages to release in the near future, for performance testing, contracts, and the like, and I'm wondering what the current story is for package release. I've heard some things about an upcoming "Cargo" package manager, so I'm wondering what the timeline on that is and whether I should be doing anything in anticipation of that, whether I should be putting things on the old Catalog, and just generally what the standard story is right now for releasing packages. Thanks, Evan

Aug. 7, 2018

Re: [Pharo-users] Pharo Launcher & Stored Settings

by Evan Donahue

Hmm, the only things I'm trying to accomplish are 1) use Pharo Launcher and 2) have each new image keep its repositories separate, as advised by others on the list, so that different images can check out different branches. Does that set up require custom scripting to adjust the repo path? The cache path does seem to do the required adjusting on its own, but the 'metacello default directory' path defaults to that crazy thing that's not a path on my computer: /builds/workspace/Pharo-6.0-Update-Step-1-Tracker PS, Is the 'store settings' button in the settings menu the standard way to configure cross-image preferences, because that seems to also save things like these paths that should be generated anew with each new image. Maybe I should stick with one single place for repos and just configure these paths to be global? Thanks -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 7, 2018

Re: [Pharo-users] transactions on pharo objects

by Carlo

Hi This research from VPRI may be useful: Worlds: Controlling the Scope of Side Effects <http://www.vpri.org/pdf/tr2011001_final_worlds.pdf> and Experiments with Worlds <http://www.vpri.org/pdf/m2013002_experiments.pdf> (Alessandro Warth, Yoshiki Ohshima, Ted Kaehler, and Alan Kay) They had a JS and Squeak version running which can be found at http://www.tinlizzie.org/~awarth/worlds/ <http://www.tinlizzie.org/~awarth/worlds/> Regards Carlo On 30 Jul 2018, at 15:16, Peter UhnÃ¡k <i.uhnak(a)gmail.com <mailto:i.uhnak@gmail.com>> wrote: Hi, is there some library or approach how to do transactions in pharo? And I don't mean database transactions, but directly in memory on Pharo objects... e.g. p := Person new. transaction do: [ p name: 'Nobody'. p age: 70. ] on: Error do: [ transaction rollback. ]. self assert: p name equals: 'Nobody'. self assert: p age equals: 70. transaction do: [ p name: 'Somebody'. p age: 1 / 0. ] on: Error do: [ transaction rollback. ]. self assert: p name equals: 'Nobody'. self assert: p age equals: 70. Any pointers appreciated. Thanks, Peter

Aug. 6, 2018

Re: [Pharo-users] BS Web and Pharo

by Esteban A. Maringolo

Ditto here, and I'm already subscribed to the newsletter! So it's not only nagging, but also superfluous. On 03/08/2018 21:42, Tim Mackinnon wrote: > Yeah - that babyâ¦ I hate seeing it over and overâ¦ presumably its some js > that a third part coughed up (badly). > > Tim > >> On 4 Aug 2018, at 00:05, CÃ©drick BÃ©ler <cdrick65(a)gmail.com >> <mailto:cdrick65@gmail.com>> wrote: >> >> I guess that one ... >> As the general warning in cookies (grrr), or the gpdr or .... >> <image1.png> >> >> EnvoyÃ© de mon iPhone >> >> Le 3 aoÃ»t 2018 Ã 22:17, Damien Pollet <damien.pollet+pharo(a)gmail.com >> <mailto:damien.pollet+pharo@gmail.com>> a Ã©critÂ : >> >>> On Thu, 2 Aug 2018 at 18:15, Tim Mackinnon <tim(a)testit.works >>> <mailto:tim@testit.works>> wrote: >>> >>> Â the constant pestering to sign up for the Pharo newsletter. >>> >>> >>> which pestering, where ? :confused:Â > -- Esteban A. Maringolo

Aug. 6, 2018

Re: [Pharo-users] Pillar Book Tester

by Siemen Baader

Very cool, this should be very useful to keep documentation up-to-date. Good job! cheers Siemen On Tue, Jul 31, 2018 at 11:25 AM Quentin DUCASSE (CI_2020) < quentin.ducasse(a)ensta-bretagne.org> wrote: > Hello everyone! > > I am currently in an internship within the RMoD team and would like to > present my work. My internship subject was the following: âHow to test > documents (books, slides) written in Pillar?â. Let me first introduce > Pillar then what I managed to implement and what is left to do. > > > > -*What is Pillar?* > > > > Pillar is a markup syntax and associated tools to write and generate > documentation, books, slide-based presentations or websites. Pillar syntax > is similar to Markdownâs one but its emphasis is stressed on publishing to > different formats/languages (Markdown, html, LateX, pdf). > > > > -*What does it mean to âtest a bookâ?* > > > -- *Display code within the book* > > Pillar syntax allows you to write codeblocks, showing a part of code. The > inside of a codeblock allows one to display any part of code you might > want to. For example: > > [[[ > > YourClass >> yourMethod > > ^ âblaâ > > ]]] > > This codeblock presents a method definition, the other two possible > codeblocks are the following: > > > Class definition > > [[[ > > Object subclass: #YourClass > > instanceVariableNames: '' > > classVariableNames: '' > > package: YourPackage' > > ]]] > > > Example > > [[[ > > 1+1 > > >>> 2 > > ]]] > > > > -- *How to test it?* > > The use of â>>>â and parameters in the codeblock will help us to test the > code within it. The BookTester will turn examples into tests. > > > > Testing examples: > > [[[testcase=true > > 3+4 becomes self assert: (3+4) equals: 7 > > >>>7 > > ]]] > > > Testing methodDefinitions and classDefinitions: > > > > Testing method or class definitions resumes is the same as testing if the > compilation of the method does not raise any error. It can help make sure > your book is up to date with the latest Pharo version. Those tests are done > the same way as testing an example: stating methodDefinition=true or > classDefinition=true as code block parameters will make them elible for > tests. Now, we are adding more features to code block or Pillar to help > book writers. > > > > -*Additional Features* > > In Pillar, several annotations can be used for different purposes like > including columns/tables/citations/figures/linksâ¦ > > > > -- * Loading code:* loader > > ${loader:account=QDucasse|project=TestBook|tag=Chapter1}$ > > allows you to load the github project as it was in the commit tagged > Chapter1. This will help you test every chapter of your code with its > current progression and also allow you to test the objects you are defining > in your book. > > > - *Executing Tests:* run > > ${run:testClass=YourClassTest}$ runs the test defined in the class > testClass. And of course this testClass can be > > > Other annotations have been added to help you write your book: > > > - * Display a class definition:* showClass: > > ${showClass:className=YourClass}$ displays a codeblock with the class > definition within it > > This helps you quickly include a class definition you want to display in > your book. Combined with the loader it means that the code can be the > source of your book. > > > > - * Display a method definition:* showMethod: > > ${showMethod:className=YourClass|methodName=yourMethod}$ will display a > codeblock with the method definition within it > > This helps you quickly include a method definition you want to display in > your book. > > > > - * Screenshot:* > > > ${showMethod:packageName=yourPackage|className=YourClass|methodName=yourMethod|caption|width|label}$ > > saves a screenshot of a Calypso browser open at the selected package, > class and method and includes it in both your book (using the designated > Pillar figure reference) and the figures subfolder in the pillar book > folder (saved as PNG). > > > -*Future objectives* > > > > One of the future improvements would be to make everyone able to write > examples and test them in the comments of method definitions. It is already > partially possible â3+4 >>> 7â will be highlighted differently and if > printed will display â7->7â. However, an automation or UI improvement would > be nice. > > > > I hope this gave you the will to write something you had in mind. Are > there any books you want to try the tools on? Feel free to ask ! > > > > Quentin Ducasse > >

Aug. 5, 2018

Volunteer for proof reading English text

by Hilaire

Hi, Since a few weeks I am writing English texts about the Dynabook. The idea is to share opinion on the topic, and see if there are interests, opinions, comments., etc. As for now I am looking at how it relates with pedagogy. Later I hope to think more on its technical dimension. However I am looking for a supplementary native English speaking native to help proof reading it. Each text is not very long, so it is not a lot of work. If you are willing to help, please email me at hilaire [at] drgeo.eu (I can't read email address from the list message as I am reading it through the gmane newsgroup and email address are encoded). Thanks Hilaire -- Dr. Geo http://drgeo.eu

Aug. 5, 2018

Re: [Pharo-users] Pharo Launcher & Stored Settings

by Sean P. DeNigris

Evan Donahue wrote > Is there a way to handle settings that should be different for every > imageâ¦ Startup script? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 5, 2018

Pharo Launcher & Stored Settings

by Evan Donahue

Is there a way to handle settings that should be different for every image when using Pharo Launcher? In particular, Settings > Software Configuraiton > Monticello > Default Local Repository & Local Cache Directory should be specific to the new image, but if I ever store settings for any reason, they get saved and incorrectly propagate to fresh images. Also, they are initialized wrong in the first place. How can I avoid this issue without manually adjusting these paths every time I make a new image? Thanks, Evan

Aug. 4, 2018

Re: [Pharo-users] Jupyter notebooks / Dynabook / JupyterTalk

by Evan Donahue

Try: Metacello new githubUser: 'jmari' project: 'JupyterTalk' commitish: 'master' path: 'repository'; baseline: 'JupyterTalk'; load -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 4, 2018

Re: [Pharo-users] Jupyter notebooks / Dynabook / JupyterTalk

by H. Hirzel

Thank you Serge, good to see that there is progress with Tensorflow and PolyMath. I have problems installing Jupytertalk into a pristine 6.1 (I follow the instructions) Metacello new baseline: 'JupyterTalk'; repository: 'github://jmari/JupyterTalk'; load:'all' gives an error message 'Could not resolve: BaselineOfJupyterTalk' Is there something else which needs to be installed first? --Hannes On 7/28/18, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > On Sat, Jul 28, 2018 at 11:21 AM H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > >> Hello >> >> What is the status of this project? >> >> >> https://github.com/jmari/JupyterTalk >> >> > âYou can ask the author of the software, Jesus Mari Aguirre. He is quite > active. > W > âe talk together about be able to use Jupytalk with Tensorflow and > PolyMath. > > He was able to reproduce part of my talk about Tensorflow: > https://htmlpreview.github.io/?https://github.com/jmari/JupyterTalk/blob/ma… > > > -- > Serge Stinckwich > UMI UMMISCO 209 (SU/IRD/UY1) > "Programs must be written for people to read, and only incidentally for > machines to execute."http://www.doesnotunderstand.org/ >

Aug. 4, 2018

Re: [Pharo-users] BS Web and Pharo

by Tim Mackinnon

Yeah - that babyâ¦ I hate seeing it over and overâ¦ presumably its some js that a third part coughed up (badly). Tim > On 4 Aug 2018, at 00:05, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> wrote: > > I guess that one ... > As the general warning in cookies (grrr), or the gpdr or .... > <image1.png> > > EnvoyÃ© de mon iPhone > > Le 3 aoÃ»t 2018 Ã 22:17, Damien Pollet <damien.pollet+pharo(a)gmail.com <mailto:damien.pollet+pharo@gmail.com>> a Ã©crit : > >> On Thu, 2 Aug 2018 at 18:15, Tim Mackinnon <tim(a)testit.works <mailto:tim@testit.works>> wrote: >> the constant pestering to sign up for the Pharo newsletter. >> >> which pestering, where ? :confused:

Aug. 4, 2018

Re: [Pharo-users] BS Web and Pharo

by CÃ©drick BÃ©ler

I guess that one ... As the general warning in cookies (grrr), or the gpdr or .... EnvoyÃ© de mon iPhone > Le 3 aoÃ»t 2018 Ã 22:17, Damien Pollet <damien.pollet+pharo(a)gmail.com> a Ã©crit : > >> On Thu, 2 Aug 2018 at 18:15, Tim Mackinnon <tim(a)testit.works> wrote: >> the constant pestering to sign up for the Pharo newsletter. > > which pestering, where ? :confused:

Aug. 3, 2018

Re: [Pharo-users] BS Web and Pharo

by Damien Pollet

On Thu, 2 Aug 2018 at 18:15, Tim Mackinnon <tim(a)testit.works> wrote: > the constant pestering to sign up for the Pharo newsletter. > which pestering, where ? :confused:

Aug. 3, 2018

Re: [Pharo-users] safely determining whether ProcessWrapper process is running

by Guillermo Polito

Hi, Sorry for the delay On Sat, Jun 30, 2018 at 7:38 PM Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Hi, > > I feel like I am missing something obvious, but is there a _safe_ way to > test if PW is still running? > I don't think so. ProcessWrapper primitives are not safe. If they are not called in the right order, of even, if one primitive fails and you call another primitive on the same object, it produces a segmentation fault. > > If the process pointer for whatever reason is no longer valid (e.g. the > image crashed / I closed image), then #isRunning results in crashing the > image. Maybe this is a bug? > > Thanks, > Peter > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 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. 3, 2018

Re: [Pharo-users] BS Web and Pharo

by Guillermo Polito

+1 I don't know how to solve it, but I agree it bothers me... Of course at some point I started ignoring it, but I imagine it can create a bad impression for people from outside the community. On Thu, Aug 2, 2018 at 6:15 PM Tim Mackinnon <tim(a)testit.works> wrote: > > Hey guys - when reading about the BS web (great article btw - > https://pxlnv.com/blog/bullshit-web/ ) it reminded me about the constant > pestering to sign up for the Pharo newsletter. > > Given I am signed up - how can I stop it always popping up? > > Itâs in the list of the BS web... so do we really need it to do this? At > least it should be a cookie that if I have it it goes away, or better still > - just put it as a menu entry and let people sign up if they like out stuff? > > Given our community fights the BS can't we lead better? > > Tim > > Sent from my iPhone > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 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. 3, 2018

BS Web and Pharo

by Tim Mackinnon

Hey guys - when reading about the BS web (great article btw - https://pxlnv.com/blog/bullshit-web/ ) it reminded me about the constant pestering to sign up for the Pharo newsletter. Given I am signed up - how can I stop it always popping up? Itâs in the list of the BS web... so do we really need it to do this? At least it should be a cookie that if I have it it goes away, or better still - just put it as a menu entry and let people sign up if they like out stuff? Given our community fights the BS can't we lead better? Tim Sent from my iPhone

Aug. 2, 2018

Re: [Pharo-users] transactions on pharo objects

by Esteban A. Maringolo

El miÃ©., 1 de ago. de 2018 20:52, Richard Sargent < richard.sargent(a)gemtalksystems.com> escribiÃ³: > Esteban A. Maringolo wrote > > As a general purpose solution if you can do that, you end up > > implementing a mini gemstone in Pharo :) > > > > But what's sure is that you should have a mini object-table of the > > "touched" objects or do "explicit" registration of these objects like > > GLORP allows you to do. > > > It seems to me that the fundamental problem with the idea of registering > each object with the transaction (or anything else) is that it requires > white-box knowledge of what every invoked behaviour will do and touch. The > above example is so minimal, it looks easy. > I agree with that. Deciding when to what to copy and what to preserve is always tricky unless yo decide to copy the whole object graph which would be terrible. Very much like what to proxy and what to forward in GemBuilder. I think if you really want transactional Smalltalk, you need to use one > designed expressly for that purpose. > (And fortunately, there is one.) > That's why I say this is tricky and you'll probably end up implementing a mini-GemStone. I don't know what it means in terms of programming, but having a transactional object memory would be a useful thing to work with. Regards, Esteban.

Aug. 2, 2018

Re: [Pharo-users] transactions on pharo objects

by Richard Sargent

Esteban A. Maringolo wrote > I think it is a tricky thing to do "in memory transactions", even > without thinking about databases. > You have to define what to keep and where to place the "original" > values (inst. vars.) of the object. > > As a general purpose solution if you can do that, you end up > implementing a mini gemstone in Pharo :) > > But what's sure is that you should have a mini object-table of the > "touched" objects or do "explicit" registration of these objects like > GLORP allows you to do. > > e.g. > > | p | > p := Person new. > System transaction: [:tx | > tx register: p. > p name: 'Nobody'. > p age: 70. > ]. It seems to me that the fundamental problem with the idea of registering each object with the transaction (or anything else) is that it requires white-box knowledge of what every invoked behaviour will do and touch. The above example is so minimal, it looks easy. I think if you really want transactional Smalltalk, you need to use one designed expressly for that purpose. (And fortunately, there is one.) > self assert: p name equals: 'Nobody'. > self assert: p age equals: 70. > > I'm using System here, to make it compatible with GemStone. > #transaction: could be implemented in terms of #beginTransaction, > #commitTransaction and internally use #abortTransaction if an > unhandled Error is signalled. > > Regards! > > Esteban A. Maringolo > El lun., 30 jul. 2018 a las 10:17, Peter UhnÃ¡k (< > i.uhnak@ > >) escribiÃ³: >> >> Hi, >> >> is there some library or approach how to do transactions in pharo? >> And I don't mean database transactions, but directly in memory on Pharo >> objects... e.g. >> >> p := Person new. >> >> transaction do: [ >> p name: 'Nobody'. >> p age: 70. >> ] on: Error do: [ >> transaction rollback. >> ]. >> >> self assert: p name equals: 'Nobody'. >> self assert: p age equals: 70. >> >> transaction do: [ >> p name: 'Somebody'. >> p age: 1 / 0. >> ] on: Error do: [ >> transaction rollback. >> ]. >> >> self assert: p name equals: 'Nobody'. >> self assert: p age equals: 70. >> >> Any pointers appreciated. >> >> Thanks, >> Peter -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 1, 2018

Re: [Pharo-users] Monticello default repositories & Iceberg

by Evan Donahue

Thanks to these replies I found the issue, but I'm not sure how to solve it. I found the start up script. I have never consciously set it, but I assume some process in the distant past automatically created it for me. The issue was that the settings for: #monticello#cacheDirectory and #monticello#defaultDirectoryName pointed to obsolete random projects from the past. I deleted them from the settings file, but it looks like when my new image autogenerated them, it stored new ones in the settings file that are equally irrelevant to future generated images: /home/myusername/Pharo/images/testimage/pharo-local/package-cache and /builds/workspace/Pharo-6.0-Update-Step-1-Tracker, respectively. What should I set these to so that they behave appropriately as I create new images in Pharo launcher? Does pharo launcher have a global dedicated place for a package cache, or is there a way to make it switch per new image? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 1, 2018

Re: [Pharo-users] Tracing Method Calls

by Peter UhnÃ¡k

If you want some projects using metalinks for inspiration: https://github.com/peteruhnak/metalinks-toolkit https://github.com/peteruhnak/live-instance-viewer (the second one also has a link to PDF explaining it in more detail) Also here an example http://blog.yuriy.tymch.uk/2016/02/vigorous-caching-in-pharo-or-how-i-used.… Peter On Wed, Aug 1, 2018 at 2:21 PM, Arturo Zambrano <arturo.zambrano(a)gmail.com> wrote: > Hi Steven > > On Fri, Jul 27, 2018 at 3:53 PM Steven Costiou <steven.costiou(a)kloum.io> > wrote: > >> Hi, >> >> it may not be actively maintained but Phantom has recently been ported to >> Pharo 6/6.1 https://github.com/InesSosa95/PHANtom >> > > that's a good news :) > >> >> >> You could also use Reflectivity (look for MetaLink class), which should >> not be hard to understand if you are familiar with aspects (although that >> is not aspects). >> >> >> >> For example, if you wanted to trace the receivers and parameters of a >> method named #mWithArg1:withArg2:withArg3: in class C, you could do : >> >> |link| >> >> link := MetaLink new. >> >> link control: #before. >> >> link arguments: #(#receiver #arguments). >> >> link metaObject: YourMetaObject. >> >> link selector: #yourMethodWithArg1:andArg:. >> >> (C lookupSelector: #mWithArg1:withArg2:withArg3:) ast link: link >> >> >> >> YourMetaObject is here an object which will receive the >> yourMethodWithArg1:andArg: with as arguments the receiver of the method >> #mWithArg1:withArg2:withArg3: and its arguments as an array. >> >> It could be a block with 2 arguments, or any other object that you would >> use to implement your trace behavior. You have a number of reifications >> available that you can pass as arguments from the context, look for >> subclasses of RFReification. >> > > I was not aware of MetaLink. Thank you! > > > > >> Steven. >> >> >> >> >> >> Le 2018-07-27 17:25, Arturo Zambrano a Ã©crit : >> >> Hi all, >> I have a piece of undocumented software that I need understand ... >> One thing I would like to do is to have a complete trace of method calls >> (receivers, parameters) for certain scenarios. >> As an "aspects"guy, my first idea was to use Phantom, but it seems not >> active anymore. >> >> Could someone please point me to some tools that I could use for this? >> (using Pharo 6, 6.1 or 7) >> >> Thanks in advance >> >> Cheers >> Arturo >> >> >> >> >> >> >> >

Aug. 1, 2018

Re: [Pharo-users] a basic hash question

by Henrik Sperre Johansen

Richard O'Keefe wrote > @James Foster: 100%. There are no exceptions. > > > On 1 August 2018 at 02:05, James Foster < > Smalltalk@ > > wrote: > >> To what extent is it required by ANSI that objects be of the same class? >> Does Pharo treat a String and a Symbol as equivalent if they have the >> same >> characters? >> >> James >> Let's not throw the baby out with the bathwater... Changing SequenceableCollection to do class comparison is a change people can get behind without much effort; especially when there's a bug that has to be resolved somehow, and it's the better overall change anyways. Forcing Strings != Symbols is a harder sell (although personally, I'd love to see it). Forcing WideStrings != ByteStrings is never going to happen; but perhaps that can be said to be compliant due to the phrasing "Unless specifically refined", and neither being defined in the standard. Interval/Array (and String/Symbol) don't have the same excuse. Cheers, Henry -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Aug. 1, 2018

Re: [Pharo-users] Tracing Method Calls

by Arturo Zambrano

Hi Steven On Fri, Jul 27, 2018 at 3:53 PM Steven Costiou <steven.costiou(a)kloum.io> wrote: > Hi, > > it may not be actively maintained but Phantom has recently been ported to > Pharo 6/6.1 https://github.com/InesSosa95/PHANtom > that's a good news :) > > > You could also use Reflectivity (look for MetaLink class), which should > not be hard to understand if you are familiar with aspects (although that > is not aspects). > > > > For example, if you wanted to trace the receivers and parameters of a > method named #mWithArg1:withArg2:withArg3: in class C, you could do : > > |link| > > link := MetaLink new. > > link control: #before. > > link arguments: #(#receiver #arguments). > > link metaObject: YourMetaObject. > > link selector: #yourMethodWithArg1:andArg:. > > (C lookupSelector: #mWithArg1:withArg2:withArg3:) ast link: link > > > > YourMetaObject is here an object which will receive the > yourMethodWithArg1:andArg: with as arguments the receiver of the method > #mWithArg1:withArg2:withArg3: and its arguments as an array. > > It could be a block with 2 arguments, or any other object that you would > use to implement your trace behavior. You have a number of reifications > available that you can pass as arguments from the context, look for > subclasses of RFReification. > I was not aware of MetaLink. Thank you! > Steven. > > > > > > Le 2018-07-27 17:25, Arturo Zambrano a Ã©crit : > > Hi all, > I have a piece of undocumented software that I need understand ... > One thing I would like to do is to have a complete trace of method calls > (receivers, parameters) for certain scenarios. > As an "aspects"guy, my first idea was to use Phantom, but it seems not > active anymore. > > Could someone please point me to some tools that I could use for this? > (using Pharo 6, 6.1 or 7) > > Thanks in advance > > Cheers > Arturo > > > > > > >

Aug. 1, 2018

Re: [Pharo-users] Pharo 7 file streams guideline

by Guillermo Polito

On Wed, Aug 1, 2018 at 11:19 AM Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > On Tue, Jul 31, 2018 at 6:41 PM Damien Pollet < > damien.pollet+pharo(a)gmail.com> wrote: > >> On Tue, 31 Jul 2018 at 18:28, Damien Pollet < >> damien.pollet+pharo(a)gmail.com> wrote: >> >>> Hi Svenâ¦ a couple questions: >>> >> >> For context, I'm considering options in Clap, for providing accessors to >> Stdio that: >> - are convenient in most cases >> - discourage users from explicitly referencing the Stdio global (so that >> one can inject other streams instead if needed) >> > > Yes. And to me it's ok if Clap defines his own good usages of streams. > Clap's usage of stream is not a typical file access. > > >> For instance, it seems to make sense to provide stdout already wrapped >> with ZnNewLineWriterStream, >> > > Also, ZnNewLineWriterStream needs only to be used when interacting with > the external word. > The rationale of keeping it separate is twofold: > - Zn* streams are meant to be reusable with other kind of streams that > are not files (such as streams in memory) where the newline conventions > do not need to be *always* enforced because the image has internally its > own convention (crs). > - Zn* streams are meant to be reusable with other kind of streams that are > not files (such as sockets) where maybe we want *also* to enforce line > ending convention. > And I'll just add that this also makes it simple to "skip" line end convention transformations. > > >> but that precludes users from buffering. >> > > Yeap. This makes me remember I tried a buffered file stream on > /dev/urandom and the buffering introduced some funny effects :) > > >> >> >> - is there a preferred order of composition between the encoding and >>> buffering streams ? If yes, it the same for read and write stream, or >>> reversed ? >>> E.g. if Stdio binaryStdin was implemented, Stdio stdin should be >>> decoded, but buffering it as well would be a problem for interactive >>> applications. >>> >>> - what's your opinion on convenience composition messages, e.g. >>> aBinaryStream buffered decoded: 'utf-8' ? >>> >>> >>> >>> On Tue, 24 Jul 2018 at 10:13, Sven Van Caekenberghe <sven(a)stfx.eu> >>> wrote: >>> >>>> >>>> >>>> > On 23 Jul 2018, at 12:07, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> > >>>> > Stdio stdout and friends just return a binary stream, hence they need >>>> wrapping for encoding. >>>> > >>>> > Maybe >>>> > >>>> > Stdio stdoutAsText >>>> > >>>> > might be an idea, but this is so uncommon that I am not sure this is >>>> a good idea. >>>> >>>> Given all remarks and comments (thanks BTW), I now think that >>>> >>>> - textual stdio streams are the more common case >>>> - binary stdio streams are the primitive ones that are seldom used >>>> - another encoding than UTF-8 seems uncommon >>>> - these are streams that exist and need no real opening/closing >>>> >>>> So, >>>> >>>> Stdio stdout >>>> >>>> should return return a character write stream with UTF-8 encoding while >>>> >>>> Stdio binaryStdout >>>> >>>> should be the lower level binary one. >>>> This would be more in line with the other streams. >>>> A non-UTF-8 encoding can be used as per Pavel's example. >>>> >>> > > -- > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > 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 > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 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. 1, 2018

Re: [Pharo-users] Pharo 7 file streams guideline

by Guillermo Polito

On Tue, Jul 31, 2018 at 6:41 PM Damien Pollet <damien.pollet+pharo(a)gmail.com> wrote: > On Tue, 31 Jul 2018 at 18:28, Damien Pollet <damien.pollet+pharo(a)gmail.com> > wrote: > >> Hi Svenâ¦ a couple questions: >> > > For context, I'm considering options in Clap, for providing accessors to > Stdio that: > - are convenient in most cases > - discourage users from explicitly referencing the Stdio global (so that > one can inject other streams instead if needed) > Yes. And to me it's ok if Clap defines his own good usages of streams. Clap's usage of stream is not a typical file access. > For instance, it seems to make sense to provide stdout already wrapped > with ZnNewLineWriterStream, > Also, ZnNewLineWriterStream needs only to be used when interacting with the external word. The rationale of keeping it separate is twofold: - Zn* streams are meant to be reusable with other kind of streams that are not files (such as streams in memory) where the newline conventions do not need to be *always* enforced because the image has internally its own convention (crs). - Zn* streams are meant to be reusable with other kind of streams that are not files (such as sockets) where maybe we want *also* to enforce line ending convention. > but that precludes users from buffering. > Yeap. This makes me remember I tried a buffered file stream on /dev/urandom and the buffering introduced some funny effects :) > > > - is there a preferred order of composition between the encoding and >> buffering streams ? If yes, it the same for read and write stream, or >> reversed ? >> E.g. if Stdio binaryStdin was implemented, Stdio stdin should be decoded, >> but buffering it as well would be a problem for interactive applications. >> >> - what's your opinion on convenience composition messages, e.g. >> aBinaryStream buffered decoded: 'utf-8' ? >> >> >> >> On Tue, 24 Jul 2018 at 10:13, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> >>> >>> > On 23 Jul 2018, at 12:07, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>> > >>> > Stdio stdout and friends just return a binary stream, hence they need >>> wrapping for encoding. >>> > >>> > Maybe >>> > >>> > Stdio stdoutAsText >>> > >>> > might be an idea, but this is so uncommon that I am not sure this is a >>> good idea. >>> >>> Given all remarks and comments (thanks BTW), I now think that >>> >>> - textual stdio streams are the more common case >>> - binary stdio streams are the primitive ones that are seldom used >>> - another encoding than UTF-8 seems uncommon >>> - these are streams that exist and need no real opening/closing >>> >>> So, >>> >>> Stdio stdout >>> >>> should return return a character write stream with UTF-8 encoding while >>> >>> Stdio binaryStdout >>> >>> should be the lower level binary one. >>> This would be more in line with the other streams. >>> A non-UTF-8 encoding can be used as per Pavel's example. >>> >> -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 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. 1, 2018