Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

I am really wonder guys. I thought you are not big funs of Object protocol. Current pinning messages are a new set of very generic messages in the Object. About Norbert idea. - bePinnedObject is not bad convention. But I would prefer the memory suffix because it reflects the low level behaviour.

Re: [Pharo-dev] argh, tests are failing!

Two other things: - if you choose to change the priority of the delivery process to the same priority as the running test process (i.e., 40) you would still need to tell the scheduler to give some chance to run to the other one. You can do that by yielding Processor yield - About timeouts:

Re: [Pharo-dev] Tricky Metaclass>>binding

> On 12 Sep 2017, at 11:32, Denis Kudriashov wrote: > > I found interesting trick in system: the way how class side perform #binding > message: > > Metaclass>>binding > "return an association that can be used as the binding >To share it between methods,

Re: [Pharo-dev] argh, tests are failing!

But the thing is that those processes you are creating for delivery are running in priority 30. This means that it may happen that they may not run any time soon (even those 200ms) if there are processes scheduled with higher priorities. So, the thing is that test is not a unit test at all. It

[Pharo-dev] Tricky Metaclass>>binding

I found interesting trick in system: the way how class side perform #binding message: Metaclass>>binding "return an association that can be used as the binding To share it between methods, reuse an existing one if possible" ^self methodDict ifEmpty: [nil -> self] ifNotEmpty: [:dict | dict anyOne

Re: [Pharo-dev] About Git support for windows

On Sun, Sep 10, 2017 at 5:06 PM, Esteban Lorenzano wrote: > > On 10 Sep 2017, at 10:56, Henrik-Nergaard wrote: > > Everyone who used filetree with metadata can tell it is super annoying and > > destroys the complete experience. > There has been a fix

[Pharo-dev] [OOPS @ SAC 2018] Extended submission deadline: Sept. 25

** OOPS 2018 Call for Papers Object-Oriented Programming Languages and Systems http://oops.disi.unige.it/OOPS18 ** Technical Track at the 33rd ACM Symposium on Applied Computing, SAC

Re: [Pharo-dev] Tricky Metaclass>>binding

I don't know... I found the idea of having a Metaclass binding strange... I mean, - metaclasses are not stored in any name dictionary such as Smalltalk - nobody references them directly in source code but by their direct classes The metaclass binding is there just for one thing really: methods

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

On 9/12/17, Denis Kudriashov wrote: > I am really wonder guys. I thought you are not big funs of Object protocol. > Current pinning messages are a new set of very generic messages in the > Object. > > About Norbert idea. > - bePinnedObject is not bad convention. >But I

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

Hi Denis, > On Sep 12, 2017, at 2:39 AM, Denis Kudriashov wrote: > > I am really wonder guys. I thought you are not big funs of Object protocol. > Current pinning messages are a new set of very generic messages in the Object. Yes, and that's because this is a fundamental

Re: [Pharo-dev] Maybe better pinning messages? (inspired by [Pinning Objects in Pharo])

Hi Eliot. I know and I only talk about new messages. I am not trying to rethink full meta model of Smalltalk. By the way #class is very common message and it is handy to use short name. But pinning messages will be used rarely in very specific applications. So no much sense to preserve them in

Re: [Pharo-dev] About Git support for windows

> > Just a random idea, how about each time writing timestamps to > a different file name "timestamps.$HashOfClassSourceFile" > Then git would never complain of a conflict(??). > If I understand your proposal correctly, that would imo result in the following: accumulating endless list of