- Pharo-users - lists.pharo.org

Re: [Pharo-users] doWithIndex: or withIndexDo: ?

by Tim Mackinnon

Yes - I like the prefix doXXX too, as I often think first of do: for normal iteration, with suffixed selectors for other variations. > On 12 Mar 2019, at 16:54, Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > #doWithIndex: for me. > > Both because it's the selector I'm used to from other dialects, and the > parameter order [:element :index | ] makes more sense to me. > > Cheers, > Henry > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

March 12, 2019

Re: [Pharo-users] doWithIndex: or withIndexDo: ?

by Henrik Sperre Johansen

#doWithIndex: for me. Both because it's the selector I'm used to from other dialects, and the parameter order [:element :index | ] makes more sense to me. Cheers, Henry -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 12, 2019

Re: [Pharo-users] complex json parsing.

by Roelof Wobben

March 12, 2019

Re: [Pharo-users] doWithIndex: or withIndexDo: ?

by Esteban Maringolo

I don't like either of those and use #keysAndValuesDo: as it is polymorphic with other collection classes. That said, I'd prefer #withIndexDo: [:each :index | ... ] because it preserves the #with:do: structure. e.g. #($a $b $c) with: (1 2 3) do: [:char :number | ... ] Regards, Esteban A. Maringolo El mar., 12 mar. 2019 a las 12:27, Oleksandr Zaytsev (<olk.zaytsev(a)gmail.com>) escribiÃ³: > Hello, > > I am working on a new collection and this question caught my interest. > Between doWithIndex: or withIndexDo:, which do you find more logical and > why? > > Oleks >

March 12, 2019

doWithIndex: or withIndexDo: ?

by Oleksandr Zaytsev

Hello, I am working on a new collection and this question caught my interest. Between doWithIndex: or withIndexDo:, which do you find more logical and why? Oleks

March 12, 2019

Pharo Days - anyone going on Wed night (3rd) and where are folks staying?

by Tim Mackinnon

Hi everyone - Iâve managed to sort out a family pass to attend Pharo Days, so keen to maximise my fun/learning/involvement. I was looking at trains on Wed afternoon - and leaving after lunch get me in Lille late afternoon - so I was wondering (if like a few years ago) any other are around earlier and going for supper (hacking code before supper) and generally socialising? Iâm also curious if others have thought about accommodation (there is lots of reasonable accommodation in Lille centre near the main station - which was pretty good last time I went) - anyone booked anything yet, and Iâll try and position myself in a similar vicinity to aid with the first question. Tim

March 12, 2019

Re: [Pharo-users] Hmmm sending at:put: to an undefined object (nil) gives a confusing error message

by Ben Coman

On Tue, 12 Mar 2019 at 21:56, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > Yes, I do not like itâ¦ I think it is there so that you can just make a variable subclass and at: / at:put: will work without > having to re-implement themâ¦ So we should consider... * how often are variable subclasses created ? by novices or experts ? * how much work is it to reimplement those methods ? how difficult to know what needs to be done ? * what is the balance cheers -ben > > Marcus > > On 12 Mar 2019, at 04:55, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > I understand #basicAt:[put:] being in Object, but I never understood #at:[put:] being there. > GNU Smalltalk: > st> nil at: 1 > Object: nil error: Invalid value nil: object not indexable > In my Smalltalk, you get a DNU. > In Squeak you get a debugger window with title > Error: instances of UndefinedObject are not indexable > The same for Boolean, Character, and Integer, > except Squeak where (20 factorial at: 1) answers 0 (oh dear oh dear oh dear). > In VW you get a "Subscript out of bounds" error, which is disappointing, > as do true and $a, but a LargePositiveinteger gets #shouldNotImplement. > > > On Tue, 12 Mar 2019 at 15:28, Tim Mackinnon <tim(a)testit.works> wrote: >> >> If you forget to initialise a variable which you thought was a Dictionary - you get a confusing error message: "Error: only integers should be used as indicesâ if you try an at:put: >> >> This is a consequence of having at:put: defined on Object (which is a bit nasty) >> >> Should UndefinedObject at least override this and signal something a bit more obvious? This is a common and easily done thing and we don't support it very well. >> >> I just did it in some code, and was scratching my head initially until I read the stack properly and realised it was something much simpler than I thought I had done. >> >> Any thoughts on this? > >

March 12, 2019

Re: [Pharo-users] [ANN] Minimal telepharo

by Ben Coman

On Tue, 12 Mar 2019 at 19:37, Norbert Hartl <norbert(a)hartl.name> wrote: > > Iâm working on having a telepharo image based on the pharo minimal image. With the help of pavel and Allex I prepared a usable artefact on github that can be used. Both images are based on Pharo8. > > The release file > > https://github.com/noha/pharo-minimal/releases/download/0.1/telepharo.zip > > contains a 32 bit minimal telepharo server image. It is 12,1 MB in size. And there is a 64 bit full pharo telepharo client image in the archive that can be used to connect to the minimal server one. I did not include the vms in the archive. These you need to install separately. > > To run the server do > > $ ./pharo server.image eval --no-quit "TlpRemoteUIManager registerOnPort: 40423â > > The client.image can be started as usual. In a playground do > > remotePharo := TlpRemoteIDE connectTo: (TCPAddress ip: #[127 0 0 1] port: 40423) > > remotePharo openPlayground. > > > To be connected to the minimal server image. Further details on telepharo you can find at > > https://github.com/pharo-ide/TelePharo > > Further relases of this will be made available at > > https://github.com/noha/pharo-minimal/releases > > Iâm planning to make a pharothings release available as well when the telepharo release is considered stable. > > Hope you like it. It will be a few weeks before I can try it, but its a really great initiative. Thanks Norbert for bringing such pieces together, as well as those providing the pieces. cheers -ben

March 12, 2019

Re: [Pharo-users] Hmmm sending at:put: to an undefined object (nil) gives a confusing error message

by Marcus Denker

Hi, Yes, I do not like itâ¦ I think it is there so that you can just make a variable subclass and at: / at:put: will work without having to re-implement themâ¦ Marcus > On 12 Mar 2019, at 04:55, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > I understand #basicAt:[put:] being in Object, but I never understood #at:[put:] being there. > GNU Smalltalk: > st> nil at: 1 > Object: nil error: Invalid value nil: object not indexable > In my Smalltalk, you get a DNU. > In Squeak you get a debugger window with title > Error: instances of UndefinedObject are not indexable > The same for Boolean, Character, and Integer, > except Squeak where (20 factorial at: 1) answers 0 (oh dear oh dear oh dear). > In VW you get a "Subscript out of bounds" error, which is disappointing, > as do true and $a, but a LargePositiveinteger gets #shouldNotImplement. > > > On Tue, 12 Mar 2019 at 15:28, Tim Mackinnon <tim(a)testit.works> wrote: > If you forget to initialise a variable which you thought was a Dictionary - you get a confusing error message: "Error: only integers should be used as indicesâ if you try an at:put: > > This is a consequence of having at:put: defined on Object (which is a bit nasty) > > Should UndefinedObject at least override this and signal something a bit more obvious? This is a common and easily done thing and we don't support it very well. > > I just did it in some code, and was scratching my head initially until I read the stack properly and realised it was something much simpler than I thought I had done. > > Any thoughts on this?

March 12, 2019

[ANN] Minimal telepharo

by Norbert Hartl

Iâm working on having a telepharo image based on the pharo minimal image. With the help of pavel and Allex I prepared a usable artefact on github that can be used. Both images are based on Pharo8. The release file https://github.com/noha/pharo-minimal/releases/download/0.1/telepharo.zip <https://github.com/noha/pharo-minimal/releases/download/0.1/telepharo.zip> contains a 32 bit minimal telepharo server image. It is 12,1 MB in size. And there is a 64 bit full pharo telepharo client image in the archive that can be used to connect to the minimal server one. I did not include the vms in the archive. These you need to install separately. To run the server do $ ./pharo server.image eval --no-quit "TlpRemoteUIManager registerOnPort: 40423â The client.image can be started as usual. In a playground do remotePharo := TlpRemoteIDE connectTo: (TCPAddress ip: #[127 0 0 1] port: 40423) remotePharo openPlayground. To be connected to the minimal server image. Further details on telepharo you can find at https://github.com/pharo-ide/TelePharo <https://github.com/pharo-ide/TelePharo> Further relases of this will be made available at https://github.com/noha/pharo-minimal/releases <https://github.com/noha/pharo-minimal/releases> Iâm planning to make a pharothings release available as well when the telepharo release is considered stable. Hope you like it, Norbert

March 12, 2019