Re: [Pharo-dev] [Pharo-users] A little prototype kernel in 9 methods :)

Nice! Is there any good reason why during cloning you do not set the delegation too? -- Pavel 2016-12-11 21:13 GMT+01:00 Stephane Ducasse : > I sent the wrong file of course. Here is the chapter :) > > > On Sun, Dec 11, 2016 at 8:52 PM,

Re: [Pharo-dev] protocol pane "no messages" Re: [Pharo-users] setter method

I will add that I doubt that any filetree repository (or at least its metadata-less versions) repository is capable of remembering an empty protocol. 2016-12-10 20:27 GMT+01:00 p...@highoctane.be : > Hi Ben, > > Yes and no. > Because you can add a protocol right away without

Re: [Pharo-dev] [Pharo-users] A little prototype kernel in 9 methods :)

Great works ! I will add some contents for Actalk chapter. BTW I update a little bit the PolyMath book. There was some sections missing. Envoyé de mon iPhone > Le 11 déc. 2016 à 20:33, stepharong a écrit : > > Hi guys > > I'm thinking to package some of my language

Re: [Pharo-dev] RBPattern matching dynamic array expressions

Hi John, thank you for our reply it is really helpful. Can you please also spend a bit of your time to talk about the “permissiveness" of the pattern syntax. For example the string '`.head `.@tail’ is parsed into a message node with selector `.@tail and a receiver variable node `.head. To my

Re: [Pharo-dev] About traits

On 12/11/16 12:06 AM, stepharong wrote: Dale I missed your remark about traits. I think that traits are nice because they act as a kind of static macro expansion and really help to get multiple inheritance into single one. Now ideally I would like to have (I hate so

Re: [Pharo-dev] NeoUUIDGenerator>>testTwoSameGenerator - intermittent CI failure

> On 11 Dec 2016, at 16:50, Ben Coman wrote: > > > > On Sun, Dec 11, 2016 at 7:49 PM, Henrik Nergaard > wrote: > >The timing problem might indeed be resolution dependent: 100us is probably > >to short sometimes. > Time microsecondClockValue

Re: [Pharo-dev] NeoUUIDGenerator>>testTwoSameGenerator - intermittent CI failure

On Sun, Dec 11, 2016 at 7:49 PM, Henrik Nergaard wrote: > >The timing problem might indeed be resolution dependent: 100us is > probably to short sometimes. > Time microsecondClockValue gives the time in microseconds, but it does not > guarantee microsecond resolution, on

Re: [Pharo-dev] NeoUUIDGenerator>>testTwoSameGenerator - intermittent CI failure

> On 11 Dec 2016, at 12:49, Henrik Nergaard wrote: > >> The timing problem might indeed be resolution dependent: 100us is probably >> to short sometimes. > Time microsecondClockValue gives the time in microseconds, but it does not > guarantee microsecond resolution,

Re: [Pharo-dev] NeoUUIDGenerator>>testTwoSameGenerator - intermittent CI failure

>The timing problem might indeed be resolution dependent: 100us is probably to >short sometimes. Time microsecondClockValue gives the time in microseconds, but it does not guarantee microsecond resolution, on windows the resolution is still in milliseconds. -- | col | col := Array

Re: [Pharo-dev] NeoUUIDGenerator>>testTwoSameGenerator - intermittent CI failure

Hi Ben, Thanks for looking into this, it was bothering me for quite some time ;-) https://pharo.fogbugz.com/f/cases/19453/NeoUUIDGenerator-testTwoSameGenerator-intermittent-CI-failure Yes, I think the counter roll-over is the problem, stupid of me to to have seen this. The timing problem

[Pharo-dev] [pharo-project/pharo-core] ebe85f: 60323

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ebe85f3731519f4db11ac58d3119708cd060c4c7 https://github.com/pharo-project/pharo-core/commit/ebe85f3731519f4db11ac58d3119708cd060c4c7 Author: Jenkins Build Server Date:

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/60323 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] About traits

> Am 11.12.2016 um 09:05 schrieb stepharong : > > >> >> Dale >> >> I missed your remark about traits. >> I think that traits are nice because they act as a kind of static macro >> expansion and really help to get multiple inheritance into single one. >> >> Now ideally

[Pharo-dev] NeoUUIDGenerator>>testTwoSameGenerator - intermittent CI failure

For Case [1] I got an unrelated CI failure [2] for NeoUUIDGeneratorTests>>#testTwoSameGenerator Checking this locally by running this a dozen times... 1 to: 1000 do: [:n| last:=n. NeoUUIDGeneratorTests new setUp testTwoSameGenerator ] Two distinct failures are apparent... 1. Takes longer than

Re: [Pharo-dev] About traits

Dale I missed your remark about traits.I think that traits are nice because they act as a kind of static macro expansion and really help to get multiple inheritance into single one. Now ideally I would like to have (I hate so much this google nonUI) - state with traits with a nice

Re: [Pharo-dev] About traits

Dale I missed your remark about traits.I think that traits are nice because they act as a kind of static macro expansion and really help to get multiple inheritance into single one. Now ideally I would like to have (I hate so much this google nonUI) - state with traits with a nice