April 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Some bugs with the last version of pharo (10281) and pharo-dev (10284)

by Nicolas Cellier

Same on Unix 2009/4/20 Damien Cassou <damien.cassou(a)gmail.com>: > On Mon, Apr 20, 2009 at 10:36 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Yes I have the same problem I cannot do copy and paste anymore on mac > > I does not work for me if I use CTRL, but it works if I use ALT. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 20, 2009

Re: [Pharo-project] About literalsDo: deprecation

by StÃ©phane Ducasse

I pushed a fix On Apr 20, 2009, at 10:15 AM, StÃ©phane Ducasse wrote: > Argh me neither. There is some black magic in MC. > I will fix that now. > > On Apr 20, 2009, at 12:15 AM, Nicolas Cellier wrote: > >> It seems that literalsDo: eem change has been reverted... >> ... in 10284 it is still deprecated ! >> I don't know why, but this makes (SystemTest testAllSentMessages) >> run forever... >> >> Please do it again >> >> >> 2009/4/18 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> Hi Nicolas >>> >>> Issue 748: literals do -> literalsDo: >>> fixed in 10280 (I wanted back these miliseconds :)). >>> >>> Stef >>> >>> On Apr 15, 2009, at 10:53 PM, Nicolas Cellier wrote: >>> >>>> I notice while scanning Eliot changes that #literalsDo: is a >>>> deprecated message... >>>> But (literals do:) replacement is not neutral concerning speed. >>>> It creates an Array where literalsDo: did not. >>>> This is not a detail because this is called on each and every >>>> method >>>> when scanning code: >>>> >>>> For example, I tried this in Pharo image: >>>> >>>> Time millisecondsToRun: [SystemNavigation default allGlobalRefs] >>>> ->5356 with Eliot's literalsDo: >>>> ->8947 pharo version calling literals do: >>>> >>>> This change spoils a few minutes out of our every day work ;) >>>> >>>> Nicolas >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 20, 2009

Re: [Pharo-project] Some bugs with the last version of pharo (10281) and pharo-dev (10284)

by Damien Cassou

On Mon, Apr 20, 2009 at 10:36 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Yes I have the same problem I cannot do copy and paste anymore on mac I does not work for me if I use CTRL, but it works if I use ALT. -- Damien Cassou http://damiencassou.seasidehosting.st

April 20, 2009

Re: [Pharo-project] Delays Semaphores and Processes

by Nicolas Cellier

I consider it is ready, see my last mail for instructions Nicolas 2009/4/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Ok let me know when this is ready and I can integrate it. > > Stef > > On Apr 19, 2009, at 9:11 PM, Nicolas Cellier wrote: > >> OK, I checked that mantis 6576 is superseded by 7321. >> >> To install DelayCleanup.1.cs it is necessary to write a ScriptLoader >> script like: >> script363 >> Â Â Â Delay startTimerEventLoop. >> Â Â Â (self buildConfigurationMapFor: >> Â Â Â #('Kernel-nice.renggli.300.mcz')) load >> >> Now, last thing to fix is remove SmallInteger maxVal//2 protection >> and test. >> >> 2009/4/19 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >>> Andreas answered that the SmallInteger limit is obsolete since >>> http://bugs.squeak.org/view.php?id=6576 which was included in 3.10 >>> >>> So I will check that mantis 6576+7321, and change the >>> DelayTests>>#testBounds >>> >>> Then only the PREAMBLE problem will remain. >>> But I see this preamble can simply go in a ScriptLoader script. >>> >>> 2009/4/19 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >>>> I took a look at http://bugs.squeak.org/view.php?id=7321 and >>>> http://code.google.com/p/pharo/issues/detail?id=688 >>>> >>>> I started publishing PharoInbox/SLICE-DelayFixFromMantis7321-nice >>>> to >>>> integrate Andreas' changes. >>>> >>>> Now I did integrate all but DelayCleanup.1.cs >>>> This change set does cure the failing testSemaphore in Pharo, but >>>> has >>>> two problems: >>>> 1) It requires a preamble, and I don't know how they are handled >>>> in Monticello >>>> 2) It probably does not include change about LargeInteger delays >>>> included in 3.9 >>>> Â (Dave kindly pointed me to http://bugs.squeak.org/view.php?id=854) >>>> 3) it makes DelayTests>>#testBounds fail >>>> >>>> >>>> I think that the limit of (SmallInteger maxVal//2) is not >>>> necessary... >>>> if LargeInteger delay fix is in the image. >>>> I can try to fix 2) mixing Andreas and Tim fixes. >>>> What about 1) ? >>>> >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 20, 2009

Re: [Pharo-project] Lots of characters lost while typing in Unix

by Damien Cassou

On Mon, Apr 20, 2009 at 10:28 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Igor this is important for importnt bug to post in the list so that I > can add them to the list of urgent stuff to integrate Sorry, my mistake: http://code.google.com/p/pharo/issues/detail?id=757 -- Damien Cassou http://damiencassou.seasidehosting.st

April 20, 2009

Re: [Pharo-project] Some bugs with the last version of pharo (10281) and pharo-dev (10284)

by StÃ©phane Ducasse

Yes I have the same problem I cannot do copy and paste anymore on mac with latest vm and latest image. Stef On Apr 20, 2009, at 9:39 AM, Laval Jannik wrote: > Hi all, > > I would like to use the new version of pharo but I have some bugs: > > Pharo-dev: > - When I open for the first time the latest version of pharo-dev, it > is impossible to use the copy-paste command > > Pharo and pharo-dev: > - it is impossible to open a Monticello browser because of an error > "invalid utf8 input detected" > - in the workspace of pharo-dev, there is the same error when I would > like to run this line in a workspace: > Installer monticello http: 'http://www.squeaksource.com'; project: > 'Moose'; install: 'MooseLoader'. > > I use the last VM (4beta1). > > Thanks for your help. > > > --- > Jannik Laval > PhD Student - Rmod Team - INRIA > Certified Project Management Associate (IPMA) > http://www.jannik-laval.eu > http://rmod.lille.inria.fr > --- > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 20, 2009

Re: [Pharo-project] Lots of characters lost while typing in Unix

by StÃ©phane Ducasse

Where? Igor this is important for importnt bug to post in the list so that I can add them to the list of urgent stuff to integrate stef On Apr 20, 2009, at 2:14 AM, Igor Stasenko wrote: > There is a mistake in update. This method is redundant. > The problem is solved by simply removing that method. A method in base > class (InputEventFetcher ) works with default 10 ms delays. > I have posted this on issue tracker. > > 2009/4/20 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >> I see, InputEventFetcher default class -> InputEventPollingFetcher >> and >> InputEventPollingFetcher>>#eventLoop >> "Fetch pending raw events from the VM. >> This method is run at high priority." >> >> | delay | >> delay := Delay forMilliseconds: 100. >> >> 100ms is very high! >> >> Pharo VM requires blockClosure, which make them recent. >> I think all these VM have primitive 93 for asynchronously signaling >> the availability of events. >> No ? >> >> 2009/4/19 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> Yes may be the event cleaning of mike cleaned too much. >>> So I hope that mike will provide a fix soon :) >>> >>> >>> Stef >>> On Apr 19, 2009, at 5:01 PM, Nicolas Cellier wrote: >>> >>>> Since latest 10284 Pharo update, i experience lost of keystroke >>>> vanishing. >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 20, 2009

Re: [Pharo-project] About literalsDo: deprecation

by StÃ©phane Ducasse

Argh me neither. There is some black magic in MC. I will fix that now. On Apr 20, 2009, at 12:15 AM, Nicolas Cellier wrote: > It seems that literalsDo: eem change has been reverted... > ... in 10284 it is still deprecated ! > I don't know why, but this makes (SystemTest testAllSentMessages) > run forever... > > Please do it again > > > 2009/4/18 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> Hi Nicolas >> >> Issue 748: literals do -> literalsDo: >> fixed in 10280 (I wanted back these miliseconds :)). >> >> Stef >> >> On Apr 15, 2009, at 10:53 PM, Nicolas Cellier wrote: >> >>> I notice while scanning Eliot changes that #literalsDo: is a >>> deprecated message... >>> But (literals do:) replacement is not neutral concerning speed. >>> It creates an Array where literalsDo: did not. >>> This is not a detail because this is called on each and every method >>> when scanning code: >>> >>> For example, I tried this in Pharo image: >>> >>> Time millisecondsToRun: [SystemNavigation default allGlobalRefs] >>> ->5356 with Eliot's literalsDo: >>> ->8947 pharo version calling literals do: >>> >>> This change spoils a few minutes out of our every day work ;) >>> >>> Nicolas >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 20, 2009

Re: [Pharo-project] Delays Semaphores and Processes

by StÃ©phane Ducasse

Ok let me know when this is ready and I can integrate it. Stef On Apr 19, 2009, at 9:11 PM, Nicolas Cellier wrote: > OK, I checked that mantis 6576 is superseded by 7321. > > To install DelayCleanup.1.cs it is necessary to write a ScriptLoader > script like: > script363 > Delay startTimerEventLoop. > (self buildConfigurationMapFor: > #('Kernel-nice.renggli.300.mcz')) load > > Now, last thing to fix is remove SmallInteger maxVal//2 protection > and test. > > 2009/4/19 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >> Andreas answered that the SmallInteger limit is obsolete since >> http://bugs.squeak.org/view.php?id=6576 which was included in 3.10 >> >> So I will check that mantis 6576+7321, and change the >> DelayTests>>#testBounds >> >> Then only the PREAMBLE problem will remain. >> But I see this preamble can simply go in a ScriptLoader script. >> >> 2009/4/19 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >>> I took a look at http://bugs.squeak.org/view.php?id=7321 and >>> http://code.google.com/p/pharo/issues/detail?id=688 >>> >>> I started publishing PharoInbox/SLICE-DelayFixFromMantis7321-nice >>> to >>> integrate Andreas' changes. >>> >>> Now I did integrate all but DelayCleanup.1.cs >>> This change set does cure the failing testSemaphore in Pharo, but >>> has >>> two problems: >>> 1) It requires a preamble, and I don't know how they are handled >>> in Monticello >>> 2) It probably does not include change about LargeInteger delays >>> included in 3.9 >>> (Dave kindly pointed me to http://bugs.squeak.org/view.php?id=854) >>> 3) it makes DelayTests>>#testBounds fail >>> >>> >>> I think that the limit of (SmallInteger maxVal//2) is not >>> necessary... >>> if LargeInteger delay fix is in the image. >>> I can try to fix 2) mixing Andreas and Tim fixes. >>> What about 1) ? >>> >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 20, 2009

Re: [Pharo-project] Delays Semaphores and Processes

by StÃ©phane Ducasse

On Apr 19, 2009, at 8:34 PM, Nicolas Cellier wrote: > Andreas answered that the SmallInteger limit is obsolete since > http://bugs.squeak.org/view.php?id=6576 which was included in 3.10 > > So I will check that mantis 6576+7321, and change the > DelayTests>>#testBounds > > Then only the PREAMBLE problem will remain. > But I see this preamble can simply go in a ScriptLoader script. yes there is no problem for adding a preamble in scriptLoader This is good that you check a bit these fixes because the topic is complex. > > > 2009/4/19 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >> I took a look at http://bugs.squeak.org/view.php?id=7321 and >> http://code.google.com/p/pharo/issues/detail?id=688 >> >> I started publishing PharoInbox/SLICE-DelayFixFromMantis7321-nice to >> integrate Andreas' changes. >> >> Now I did integrate all but DelayCleanup.1.cs >> This change set does cure the failing testSemaphore in Pharo, but has >> two problems: >> 1) It requires a preamble, and I don't know how they are handled in >> Monticello >> 2) It probably does not include change about LargeInteger delays >> included in 3.9 >> (Dave kindly pointed me to http://bugs.squeak.org/view.php?id=854) >> 3) it makes DelayTests>>#testBounds fail >> >> >> I think that the limit of (SmallInteger maxVal//2) is not >> necessary... >> if LargeInteger delay fix is in the image. >> I can try to fix 2) mixing Andreas and Tim fixes. >> What about 1) ? >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 20, 2009