January 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Ann] ReadWriteLock

by Denis Kudriashov

2016-01-05 17:25 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > Comment inside #critical: method said that we should signal in any case. I think I not correctly understand this point when read it. Process terminating case is not mention in comment.

Jan. 5, 2016

Re: [Pharo-dev] [Ann] ReadWriteLock

by Denis Kudriashov

I found problem. Look at Process>>terminate. There is special place: "Figure out if we are terminating the process while waiting in > Semaphore>>critical: > In this case, pop the suspendedContext so that we leave the ensure: block > inside > Semaphore>>critical: without signaling the semaphore." > (oldList class == Semaphore and: [ > self halt. > suspendedContext method == (Semaphore compiledMethodAt: #critical:) ]) > ifTrue: [ > suspendedContext := suspendedContext home ]. Really crazy. Comment inside #critical: method said that we should signal in any case. But #terminate method said that we should not allow signalling in that case. Why it is not implemented inside #critical: method by #ifCurtailed: logic? 2016-01-05 17:10 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > > 2016-01-05 16:54 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> 2016-01-05 16:06 GMT+01:00 Ben Coman <btc(a)openinworld.com>: >> >>> This is really strange! Why does the copied class Semaphore2 behave >>> differently to the original class Semaphore? This was in build 50510. >>> >> >> It is so frustrating. >> I add tests for your cases which is red now. And one for Semaphore >> (inside ReadWriteLockTests) which is green >> > > It is really crazy. I just try two experiments: > 1) I move semaphore critical: logic to Mutex. Our test with mutex become > red. > 2) I copy Semaphore>>critical: to #critical2:. And with it Semaphore test > become red. > > So somebody definitely know about #critical: selector and it receiver >

Jan. 5, 2016

Re: [Pharo-dev] Catalog statistics (Who know this projects?)

by Esteban Lorenzano

> On 05 Jan 2016, at 17:06, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 05-01-16 16:56, Esteban Lorenzano wrote: >> >>> On 05 Jan 2016, at 16:51, Stephan Eggermont <stephan(a)stack.nl> wrote: >>> >>> On 05-01-16 16:21, Esteban Lorenzano wrote: >>>> Soâ¦ I took a couple of minutes to do a small list of project description status: >>>> >>>> From a total of 379 projects currently in the catalog, just 115 have a description and/or keywords associated. >>>> Which means 264 are mysterious projects nobody can guess what are they about. >>>> >>>> I was thinking most of this projects would be in Unsorted (or Pharo 3), but I found that many are also on Pharo 5 and 4â¦. which is frankly unacceptable :) >>>> Even very important projects like Seaside or Garage and Glorp are not documented. >>>> >>>> So, please peopleâ¦ take a look at your projects and PLEASE, provide a description and proper keywordsâ¦ Nobody can guess what is Aconcagua (besides a cool mountain in south america), or Telescope, etc., etc., etc. >>>> >>>> Here the list of non-documented projects: >>> >>> ss3 has no projects? >> >> catalog just catalogs projects in the MetaRepos >> you project can live where he wants, but configuration needs to be copied into MetaRepoForPharoXX >> >> thatâs how always was, and thatâs what catalog shows :) > > http://ss3.gemtalksystems.com/ss/MetaRepoForPharo20 <http://ss3.gemtalksystems.com/ss/MetaRepoForPharo20> hmmmâ¦ didnât remember that existed :) but i was even considering propose you to deprecate the unsorted repository (a lot of obsolete projects there)â¦ Esteban > > Stephan

Jan. 5, 2016

Re: [Pharo-dev] [Ann] ReadWriteLock

by Denis Kudriashov

2016-01-05 16:54 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > 2016-01-05 16:06 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > >> This is really strange! Why does the copied class Semaphore2 behave >> differently to the original class Semaphore? This was in build 50510. >> > > It is so frustrating. > I add tests for your cases which is red now. And one for Semaphore (inside > ReadWriteLockTests) which is green > It is really crazy. I just try two experiments: 1) I move semaphore critical: logic to Mutex. Our test with mutex become red. 2) I copy Semaphore>>critical: to #critical2:. And with it Semaphore test become red. So somebody definitely know about #critical: selector and it receiver

Jan. 5, 2016

Re: [Pharo-dev] Catalog statistics (Who know this projects?)

by Stephan Eggermont

On 05-01-16 16:56, Esteban Lorenzano wrote: > >> On 05 Jan 2016, at 16:51, Stephan Eggermont <stephan(a)stack.nl> wrote: >> >> On 05-01-16 16:21, Esteban Lorenzano wrote: >>> Soâ¦ I took a couple of minutes to do a small list of project description status: >>> >>> From a total of 379 projects currently in the catalog, just 115 have a description and/or keywords associated. >>> Which means 264 are mysterious projects nobody can guess what are they about. >>> >>> I was thinking most of this projects would be in Unsorted (or Pharo 3), but I found that many are also on Pharo 5 and 4â¦. which is frankly unacceptable :) >>> Even very important projects like Seaside or Garage and Glorp are not documented. >>> >>> So, please peopleâ¦ take a look at your projects and PLEASE, provide a description and proper keywordsâ¦ Nobody can guess what is Aconcagua (besides a cool mountain in south america), or Telescope, etc., etc., etc. >>> >>> Here the list of non-documented projects: >> >> ss3 has no projects? > > catalog just catalogs projects in the MetaRepos > you project can live where he wants, but configuration needs to be copied into MetaRepoForPharoXX > > thatâs how always was, and thatâs what catalog shows :) http://ss3.gemtalksystems.com/ss/MetaRepoForPharo20 Stephan

Jan. 5, 2016

Re: [Pharo-dev] [Ann] ReadWriteLock

by Denis Kudriashov

2016-01-05 16:06 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > btw I have this growing suspicion that we should eliminate > Semaphore>>critical: and Semaphore>>forMutualExclusion. Semaphores > on their own should *not* provide a facility for to protect critical > regions since they suffer from accidental release [1] due to > *lack*of*ownership*. > I have same feeling when analyse problem of critical: implementation. But I not think that Semaphore>>forMutualExclusion is bad. It is common case that semaphore "free" by default. And this name is explicitly said about this.

Jan. 5, 2016

Re: [Pharo-dev] Catalog statistics (Who know this projects?)

by Esteban Lorenzano

> On 05 Jan 2016, at 16:51, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 05-01-16 16:21, Esteban Lorenzano wrote: >> Soâ¦ I took a couple of minutes to do a small list of project description status: >> >> From a total of 379 projects currently in the catalog, just 115 have a description and/or keywords associated. >> Which means 264 are mysterious projects nobody can guess what are they about. >> >> I was thinking most of this projects would be in Unsorted (or Pharo 3), but I found that many are also on Pharo 5 and 4â¦. which is frankly unacceptable :) >> Even very important projects like Seaside or Garage and Glorp are not documented. >> >> So, please peopleâ¦ take a look at your projects and PLEASE, provide a description and proper keywordsâ¦ Nobody can guess what is Aconcagua (besides a cool mountain in south america), or Telescope, etc., etc., etc. >> >> Here the list of non-documented projects: > > ss3 has no projects? catalog just catalogs projects in the MetaRepos you project can live where he wants, but configuration needs to be copied into MetaRepoForPharoXX thatâs how always was, and thatâs what catalog shows :) Esteban > > Stephan > > >

Jan. 5, 2016

Re: [Pharo-dev] [Ann] ReadWriteLock

by Denis Kudriashov

Hi Thank you very much for this analysts. 2016-01-05 16:06 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > This is really strange! Why does the copied class Semaphore2 behave > differently to the original class Semaphore? This was in build 50510. > It is so frustrating. I add tests for your cases which is red now. And one for Semaphore (inside ReadWriteLockTests) which is green

Jan. 5, 2016

Re: [Pharo-dev] Catalog statistics (Who know this projects?)

by Stephan Eggermont

On 05-01-16 16:21, Esteban Lorenzano wrote: > Soâ¦ I took a couple of minutes to do a small list of project description status: > > From a total of 379 projects currently in the catalog, just 115 have a description and/or keywords associated. > Which means 264 are mysterious projects nobody can guess what are they about. > > I was thinking most of this projects would be in Unsorted (or Pharo 3), but I found that many are also on Pharo 5 and 4â¦. which is frankly unacceptable :) > Even very important projects like Seaside or Garage and Glorp are not documented. > > So, please peopleâ¦ take a look at your projects and PLEASE, provide a description and proper keywordsâ¦ Nobody can guess what is Aconcagua (besides a cool mountain in south america), or Telescope, etc., etc., etc. > > Here the list of non-documented projects: ss3 has no projects? Stephan

Jan. 5, 2016

Re: [Pharo-dev] Syntax Highlighting error (RBParseErrorNode(Object)>>doesNotUnderstand: #isInstance)

by Sven Van Caekenberghe

Cool. I just merged it and I can confirm that it solves my issue. > On 05 Jan 2016, at 16:19, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > yes, > > this is fixed by > > https://pharo.fogbugz.com/f/cases/17276/Semantic-Analysis-needs-refactoring > > I am now back from holidays and will review/intergrate this soon. > > >> On 05 Jan 2016, at 16:15, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> I am seeing the following very annoying error in 50511 spur. >> >> Open a Playground, >> type [ (both open en close are inserted, with the cursor in-between), >> type : (to start a block arg), >> boom: >> >> RBParseErrorNode(Object)>>doesNotUnderstand: #isInstance >> OCASTClosureAnalyzer>>changeVariableClass: >> OCASTClosureAnalyzer>>visitArgumentNode: >> [ :each | self visitArgumentNode: each ] in OCASTClosureAnalyzer(RBProgramNodeVisitor)>>visitArgumentNodes: >> OrderedCollection>>do: >> OCASTClosureAnalyzer(RBProgramNodeVisitor)>>visitArgumentNodes: >> OCASTClosureAnalyzer>>visitBlockNode: >> RBBlockNode>>acceptVisitor: >> OCASTClosureAnalyzer(RBProgramNodeVisitor)>>visitNode: >> [ :each | self visitNode: each ] in OCASTClosureAnalyzer(RBProgramNodeVisitor)>>visitSequenceNode: >> OrderedCollection>>do: >> OCASTClosureAnalyzer(RBProgramNodeVisitor)>>visitSequenceNode: >> RBSequenceNode>>acceptVisitor: >> OCASTClosureAnalyzer(RBProgramNodeVisitor)>>visitNode: >> OCASTClosureAnalyzer>>visitMethodNode: >> RBMethodNode>>acceptVisitor: >> OCASTClosureAnalyzer(RBProgramNodeVisitor)>>visitNode: >> OCASTSemanticAnalyzer>>analyze: >> RBMethodNode>>doSemanticAnalysis >> RBBlockNode(RBProgramNode)>>doSemanticAnalysis >> RubSHTextStylerST80(SHRBTextStyler)>>privateStyle: >> [ self privateStyle: text. >> view ifNotNil: [ view stylerStyledInBackground: text ] ] in [ backgroundProcess := [ self privateStyle: text. >> view ifNotNil: [ view stylerStyledInBackground: text ] ] >> forkAt: Processor userBackgroundPriority ] in RubSHTextStylerST80(SHTextStyler)>>styleInBackgroundProcess: >> [ self value. >> Processor terminateActive ] in BlockClosure>>newProcess >> >> Has this already been reported ? >> >> It makes the image almost unusable... >> >> Sven >> >> > >

Jan. 5, 2016