- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [pharo-project/pharo-core] aff0e7: 50589

by Sven Van Caekenberghe

> On 18 Feb 2016, at 17:08, GitHub <noreply(a)github.com> wrote: > > Log Message: > ----------- > 50589 > 17511 Inline temporary smart suggestion crashes > https://pharo.fogbugz.com/f/cases/17511 > > 17606 Zn Update Februari 2016 > https://pharo.fogbugz.com/f/cases/17606 > > 17015 Failing test: SetTest>>#testAllSetsAreHealthy > https://pharo.fogbugz.com/f/cases/17015 > > 17590 Textmenu in Finder code pane does not work. > https://pharo.fogbugz.com/f/cases/17590 > > http://files.pharo.org/image/50/50589.zip Thank you, this time everything went smooth: the CI validation check went OK the first time + everything integrated the same day !

Feb. 19, 2016

Re: [Pharo-dev] mutex optimisation - #ifTrue:ifFalse versus #ifNil:ifNotNil: [ignore last post]

by Ben Coman

Whoops, sorry, that last post shot off half done. Please delete it.

Feb. 19, 2016

mutex optimisation - #ifTrue:ifFalse versus #ifNil:ifNotNil:

by Ben Coman

The Mutex primitives return a tri-state value: true, false and nil. So we would have... NewMutex>>critical: mutuallyExcludedBlock ifLocked: alternativeBlock ^lock tryAcquire ifNil: mutuallyExcludedBlock ifNotNil: [:acquired| acquired ifTrue: [mutuallyExcludedBlock ensure: [lock strictRelease]] ifFalse: alternativeBlock ]. NewMutex>>critical: mutuallyExcludedBlock ^lock waitAcquire ifNil: mutuallyExcludedBlock ifNotNil:[ mutuallyExcludedBlock ensure: [lock strictRelease] ]. So we would have NewMutex>>critical: aBlock ifLocked: lockedBlock ^lock tryAcquire ifNil: mutuallyExcludedBlock ifNotNil: [:acquired | acquired ifTrue: [mutuallyExcludedBlock ensure: [lock strictRelease]] ifFalse: alternativeBlock ]. Mutex>>critical: aBlock ifLocked: lockedBlock ^self primitiveTestAndSetOwnershipOfCriticalSection ifNil: [lockedBlock value] ifNotNil:[:alreadyOwner| alreadyOwner ifTrue: [aBlock value] ifFalse: [aBlock ensure: [self primitiveExitCriticalSection]]] ifNil:ifNotNil: Also, I notice several of RBMessageNode>>isInlineXXXX methods contain... self receiver isBlock ifTrue: [^ false]. Does this mean that... [ true ] ifTrue: [2] ifFalse: [3] is not inlined?

Feb. 19, 2016

FFI related musings

by Ben Coman

While musing on FFI interfacing issues like C++ name mangling, I found an interesting article "Beautiful Native Libraries" about the other side of the fence of designing a nice library interface. I learnt some things maybe of interest to others - perhaps for pushing upstream into external libraries to ease their use by our FFI. http://lucumr.pocoo.org/2013/8/18/beautiful-native-libraries/ Some of the ideas seem applicable to maybe one day helping the VM be embeddable in other programs. Also, for the occasional idea of in-Image parsing of C include files, a link to a basic algorithm for macro expansion. http://www.spinellis.gr/blog/20060626/ And while I haven't read the following, it was interesting to skim "Calling conventions for different C++ compilers and operating systems" http://www.agner.org/optimize/calling_conventions.pdf cheers -ben

Feb. 19, 2016

Re: [Pharo-dev] [squeak-dev] Process>>isSusended

by David T. Lewis

On Thu, Feb 18, 2016 at 10:03:47PM -0500, David T. Lewis wrote: > On Thu, Feb 18, 2016 at 01:22:28PM -0800, Eliot Miranda wrote: > > Hi All, > > > > we have a serious misunderstanding in current versions of Squeak's and > > Pharo's Process>>isSuspended. > > > > Squeak's version reads > > > > isSuspended > > ^myList isNil > > > > Pharo's reads > > > > isSuspended > > ^myList isNil or: [ myList isEmpty ] > > > > Process's myList holds the list a process is on when it is not running. > > There is only one running process at any one time, Processor > > activeProcess. The active process's myList is always nil, so Squeak's and > > Pharo's are both wrong for the active process. > > > > Processor activeProcess isSuspended => true (!!!) > > This was working correctly as of Squeak4.6, but not in Squeak5.0.15113.image. Correcting myself, the difference in behavior is related to the VM. Using a Squeak 4.6 image and comparing Cog versus interpreter VM: Processor activeProcess isSuspended ==> true "Cog" Processor activeProcess isSuspended ==> false "interpreter VM" I think there were some process scheduling improvements introduced in Cog, and maybe the image needs to be adjusted accordingly? Dave

Feb. 19, 2016

Re: [Pharo-dev] [squeak-dev] Process>>isSusended

by David T. Lewis

On Thu, Feb 18, 2016 at 01:22:28PM -0800, Eliot Miranda wrote: > Hi All, > > we have a serious misunderstanding in current versions of Squeak's and > Pharo's Process>>isSuspended. > > Squeak's version reads > > isSuspended > ^myList isNil > > Pharo's reads > > isSuspended > ^myList isNil or: [ myList isEmpty ] > > Process's myList holds the list a process is on when it is not running. > There is only one running process at any one time, Processor > activeProcess. The active process's myList is always nil, so Squeak's and > Pharo's are both wrong for the active process. > > Processor activeProcess isSuspended => true (!!!) This was working correctly as of Squeak4.6, but not in Squeak5.0.15113.image. Dave

Feb. 19, 2016

Re: [Pharo-dev] [ANN] The Pharo Unicode Project

by Mariano Martinez Peck

Wow guys. Unbelievable. Amazing. Coming from you and Henry, I really don't expect anything else than this :) Sven I also love your midium posts. Thanks!!! On Thu, Feb 18, 2016 at 6:22 PM, stepharo <stepharo(a)free.fr> wrote: > I ***LOVE*** the documentation :) > > > Le 17/2/16 10:16, Sven Van Caekenberghe a Ã©crit : > > Hi, >> >> In Pharo we can deal with and represent any Unicode character and string, >> but there are still some important pieces of functionality missing. >> >> The goal of the Pharo Unicode project is to gradually improve and expand >> Unicode support in Pharo. We started in December last year to lay the >> foundation and are now ready to go public with what we built. >> >> The first delivery is an implementation of Unicode Normalization, >> together with an implementation of the Unicode Character Database. >> >> Please read the following article for more information (the appendix >> explains how to get the code). >> >> An Implementation of Unicode Normalisation >> >> Streaming NFC, NFD, NFKC & NFKD, normalization QC and normalization >> preserving concatenation. >> >> >> https://medium.com/concerning-pharo/an-implementation-of-unicode-normalizat… >> >> The development branch also contains a work in progress implementation of >> Unicode Collation. >> >> Much work remains to be done and contributions are more than welcome. >> >> Sven & Henrik >> >> > > -- Mariano http://marianopeck.wordpress.com

Feb. 19, 2016

Re: [Pharo-dev] [ANN] The Pharo Unicode Project

by stepharo

I deeply appreciate your effort! Le 17/2/16 23:27, Sven Van Caekenberghe a Ã©crit : >> On 17 Feb 2016, at 19:56, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> >> I read the whole Article, seems like a tricky, to not say hard, subject. > Yes. The Unicode specs are big and complex. Step one is to read & understand them, at least well enough to find your way. Doing some implementation is not too hard, but getting 100% scores on the very extensive test suites was/is quite hard. > >> The article is very detailed and well written though. > Thx. > >> What is the rationale behind embracing such a challenging feature like supporting Unicode? > Unicode is the de facto standard for internationalisation of computer software. Any serious platform has to tackle (big parts of) Unicode. > >> Regards! >> >> >> Esteban A. Maringolo >> >> >> 2016-02-17 15:24 GMT-03:00 Max Leske <maxleske(a)gmail.com>: >>> Good stuff guys! >>> >>>> On 17 Feb 2016, at 10:16, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >>>> >>>> Hi, >>>> >>>> In Pharo we can deal with and represent any Unicode character and string, but there are still some important pieces of functionality missing. >>>> >>>> The goal of the Pharo Unicode project is to gradually improve and expand Unicode support in Pharo. We started in December last year to lay the foundation and are now ready to go public with what we built. >>>> >>>> The first delivery is an implementation of Unicode Normalization, together with an implementation of the Unicode Character Database. >>>> >>>> Please read the following article for more information (the appendix explains how to get the code). >>>> >>>> An Implementation of Unicode Normalisation >>>> >>>> Streaming NFC, NFD, NFKC & NFKD, normalization QC and normalization preserving concatenation. >>>> >>>> https://medium.com/concerning-pharo/an-implementation-of-unicode-normalizat… >>>> >>>> The development branch also contains a work in progress implementation of Unicode Collation. >>>> >>>> Much work remains to be done and contributions are more than welcome. >>>> >>>> Sven & Henrik >>> > >

Feb. 18, 2016

Process>>isSusended

by Eliot Miranda

Hi All, we have a serious misunderstanding in current versions of Squeak's and Pharo's Process>>isSuspended. Squeak's version reads isSuspended ^myList isNil Pharo's reads isSuspended ^myList isNil or: [ myList isEmpty ] Process's myList holds the list a process is on when it is not running. There is only one running process at any one time, Processor activeProcess. The active process's myList is always nil, so Squeak's and Pharo's are both wrong for the active process. Processor activeProcess isSuspended => true (!!!) A process may be runnable, but not running (which follows form there being only one running process, the active process, at any one time). If it is runnable but not running its list is one of the runnable process lists in the scheduler, e.g. Processor waitingProcessesAt: Processor activePriority => a LinkedList() Processor waitingProcessesAt: Processor lowestPriority => a LinkedList(a Process in ProcessorScheduler class>>idleProcess) Here's a couple of illustrative examples: [Semaphore new wait] fork suspendingList => a LinkedList(a Process in [] in BlockClosure>>newProcess) ([Semaphore new wait] forkAt: Processor activePriority + 1) suspendingList => a Semaphore(a Process in [] in UndefinedObject>>DoIt) In the first example above the new process isn't running yet. It's runnable but hasn't got a chance to run because the active process that created it is still running. So the process's list is Processor waitingProcessesAt: Processor activePriority. In the second example the process has got to run, because, having higher priority, it has preempted the active process that created it. So it suspends waiting on the semaphore. So in fact, isSuspended should read something like isSuspended | myRunList | myRunList := Processor waitingProcessesAt: priority. ^myList notNil and: [myList ~~ myRunList] except that this isn't atomic. But it isn't the complete nonsense we have at the moment. Here's an atomic version that answers the truth at the point that the question was asked: isSuspended | myPriority | myPriority := priority. ^myList ifNil: [false] ifNotNil: [:list| list ~~ (Processor waitingProcessesAt: myPriority)] We need tests like self deny: Processor activeProcess isSuspended. self deny: ([Semaphore new wait] forkAt: Processor activePriority) isSuspended. self assert: ([Semaphore new wait] forkAt: Processor activePriority + 1) isSuspended. _,,,^..^,,,_ best, Eliot

Feb. 18, 2016

Re: [Pharo-dev] [ANN] The Pharo Unicode Project

by stepharo

I ***LOVE*** the documentation :) Le 17/2/16 10:16, Sven Van Caekenberghe a Ã©crit : > Hi, > > In Pharo we can deal with and represent any Unicode character and string, but there are still some important pieces of functionality missing. > > The goal of the Pharo Unicode project is to gradually improve and expand Unicode support in Pharo. We started in December last year to lay the foundation and are now ready to go public with what we built. > > The first delivery is an implementation of Unicode Normalization, together with an implementation of the Unicode Character Database. > > Please read the following article for more information (the appendix explains how to get the code). > > An Implementation of Unicode Normalisation > > Streaming NFC, NFD, NFKC & NFKD, normalization QC and normalization preserving concatenation. > > https://medium.com/concerning-pharo/an-implementation-of-unicode-normalizat… > > The development branch also contains a work in progress implementation of Unicode Collation. > > Much work remains to be done and contributions are more than welcome. > > Sven & Henrik >

Feb. 18, 2016