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

Re: [Pharo-project] About testing that ensure works

by StÃ©phane Ducasse

good suggestion. I will check that. Stef On Apr 26, 2011, at 3:11 PM, Henrik Sperre Johansen wrote: > On 24.04.2011 12:05, StÃ©phane Ducasse wrote: >>> i am puzzled. You wanna to be sure that ensure block are executed? >>> It is. >> I want to write a test that shows and tests the withOrganizer:do: semantics. >> In particular that the ensure is executed and that the context set by the withOrganizer: is only present >> in the do: block. >> > In other words, another use case probably written more cleanly using the non-existing > Announcer >> #suspend: subscriber while: aBlock > > ;) > > Cheers, > Henry >

April 26, 2011

Re: [Pharo-project] Error with latest ProfStef in Pharo 1.3

by Alexandre Bergel

Thanks Laurent & Patrick, it was cool! Alexandre On 25 Apr 2011, at 16:31, Alexandre Bergel wrote: > Ok, tomorrow at 13:20 - 13:30 (GMT+1) on skype > > Alexandre > > > On 25 Apr 2011, at 15:26, laurent laffont wrote: > >> >> On Mon, Apr 25, 2011 at 8:30 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> May be I can check this with my local developer group on Tuesday (we meet from 12:30 -> 13h30. If you wake up early :) >> >> 13:30 in france is 8:30 in Chile. I usually arrive at 8:20 at work. So, we meet on tomorrow? >> Using IRC? >> >> No problem. We can use skype. >> >> Laurent. >> >> >> >> Cheers, >> Alexandre >> >>> Laurent >>> >>> We could then write new tests, make sure ProfStef works for Pharo 1.3 and fix the bug found by Mariano. >>> >>> Cheers, >>> Alexandre >>> >>> >>> On 24 Apr 2011, at 12:33, laurent laffont wrote: >>> >>>> >>>> On Sun, Apr 24, 2011 at 6:43 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>> ah ah! This is what we have changed during the pharo cast. >>>> Laurent, do you want that we have a look at it together? >>>> >>>> haha I won't be able to look at it until Tuesday. >>>> >>>> Laurent. >>>> >>>> >>>> Cheers, >>>> Alexandre >>>> >>>> >>>> On 24 Apr 2011, at 11:30, Mariano Martinez Peck wrote: >>>> >>>>> "Error 'Please use buildTutorialTopicFor: instead'" >>>>> >>>>> when I try to open it from the menu. >>>>> >>>>> ProfStefHelpTutorialBuilder >> buildHelpTopicFrom: aHelpTopicDescription >>>>> "Start building from the given help topic description" >>>>> >>>>> ^(self new) >>>>> rootToBuildFrom: aHelpTopicDescription; >>>>> build; >>>>> topicToBuild >>>>> >>>>> the rpoblem is that #new >>>>> >>>>> I am using last versions of Pharo1.3 >>>>> >>>>> -- >>>>> Mariano >>>>> http://marianopeck.wordpress.com >>>>> >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 26, 2011

Re: [Pharo-project] Henrik should we include Settings-Sound ?

by StÃ©phane Ducasse

but henrik I would not rever the change. If I remember correctly I change them because they were incorrect. Stef > On 24.04.2011 15:57, Mariano Martinez Peck wrote: >> I saw that package in PharoSound and I wonder if it should be added to the Metacello conf >> >> cheers >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > Yes, in a version 4.0 for 1.1 and 1.3 together with Sound-MarianoMartinezPeck.65 , as soon as we revert some stuff that was done in base which broke it. > IE. change registration back to working with instances, and soundEnabled to use a class var of SoundService rather than that of it's registered class. > > It will not work with the code based on branch from PharoTaskForces (Sound-MarianoMartinezPeck.64), as that one just deleted all preferences rather than preserve them in a functionally correct way. > > Cheers, > Henry >

April 26, 2011

Re: [Pharo-project] What is a well documented class?

by Alexandre Bergel

> What would be a "casual user" of a class in Smalltalk? Someone who does not care about the type of instances variables of that particular class :-) Alexandre > > > Em 25/04/2011 18:19, Alexandre Bergel < alexandre.bergel(a)me.com > escreveu: > Ok, focusing on the instance variables. I think there is two kind of documentation, one for the casual user, and another for the developers. > > Alexandre > > > On 25 Apr 2011, at 16:09, DougEdmunds wrote: > >> 2cents about "what is a well-documented class?": >> >> Information about the state variables (instance variables): what goes in the >> slot, and what it's for. >> >> Good examples (the layout gets skewed doing copy/paste) >> >> in RxsPredicate >> >> Instance Variables: >> >> predicate A one-argument block. If it evaluates to the value >> defined by >> when it is passed a character, the predicate is considered to >> match. >> >> negation A one-argument block that is a negation of >> . >> >> >> SMxMorph >> >> Structure: >> instance var Type Description >> bounds Rectangle A Rectangle indicating my position and a size that will >> enclose me. >> >> owner SMxMorph My parent SMxMorph, or nil for the top-level SMxMorph, >> which is a >> or nil world, typically a SMxPasteUpMorph. >> >> submorphs Array My child Morphs. >> >> fullBounds Rectangle A Rectangle minimally enclosing me and my >> submorphs. >> >> color Color My primary color. Subclasses can use this in different >> ways. >> >> extension SMxMorphExtension Allows extra properties to be stored without >> adding a >> or nil storage burden to all morphs. >> >> >> -- >> View this message in context: http://forum.world.st/What-is-a-well-documented-class-tp3470956p3474024.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 26, 2011

Re: [Pharo-project] About testing that ensure works

by Henrik Sperre Johansen

On 24.04.2011 12:05, StÃ©phane Ducasse wrote: >> i am puzzled. You wanna to be sure that ensure block are executed? >> It is. > I want to write a test that shows and tests the withOrganizer:do: semantics. > In particular that the ensure is executed and that the context set by the withOrganizer: is only present > in the do: block. > In other words, another use case probably written more cleanly using the non-existing Announcer >> #suspend: subscriber while: aBlock ;) Cheers, Henry

April 26, 2011

Re: [Pharo-project] Better debugging...

by Alexandre Bergel

> In Pinocchio[1] we implemented very nice and simple debuggers by "just" changing the current interpreter to take a user-action into account on each message send. Since this is implemented on top of a metacircular interpreter this was quite simple to achieve. So the whole implementation of the known debugger functionality (step, over...) maybe took an afternoon. Since you have access to the full interpreter protocol it is very easy to intercept different sorts of actions. As described in the linked paper, it was very easy to implement the object-flow behavior in Pinocchio. I have built a number of code profilers over the time. The instrumentation is done with Spy, a kind of method wrapper. It would cool to see whether Pinocchio can be a better replacement for my profilers. This will be a cool validation for Pinocchio Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 26, 2011

Re: [Pharo-project] About testing that ensure works

by Henrik Sperre Johansen

On 24.04.2011 14:13, StÃ©phane Ducasse wrote: > Ok I got it I ws confused by SUnit interference > > testDo > "self run: #testDo" > > self do: [ Error signal]. > self assert: x = 3 > > > > self run: #testDo -> red tests > > self debug: #testDo + proceed -> green tests The ensure runs, but at that point the test already failed, see it says "1 errors", not "1 failures" :) To see it manually, you could put Transcript show: 'Foo' or some such in the ensure block instead, and notice how the Transcript is written :) Cheers, Henry ps. It's easier to just write aBlock ensure: [blabla] instead of [aBlock value] ensure: [blabla] ... if aBlock REALLY is a block, and not aValuable, of course :=

April 26, 2011

Re: [Pharo-project] petit parser help

by Ricardo Moran

Hi Lukas, thanks for answering! Since all this stuff is pretty new to me sometimes is hard to see when something is an optimization or the right way to do it :) Cheers, Richo On Tue, Apr 26, 2011 at 2:27 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > > I only played a little with PetitParser but I think the answer is in > > PetitXml>>#element. You see in the action block that it compares the > > "qualified" of the open and close tags and if they're different it > returns a > > PPFailure. It also takes care of the inlineTag in the same block by > asking > > if the fifth node is '/>'. > > This "taking care of the inlineTag" is just an ugly optimization, but > it makes the parser extremely fast :-) > > Ideally you start with a grammar as you propose and add then check if > open and close tag are the same in the callback, as in the example > above. > > Another subtlety that you see in the above example that is the parser: > > [ :stream | stream position ] asParser > > This object returns the position in the stream and makes it possible > to create the failure at the beginning of the close tag. Again, this > is not required to start with. You can create the failure object like > below, it just will not point you to the right place in the input > then: > > PPFailure message: 'tags not matching' at: 0 > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > >

April 26, 2011

Re: [Pharo-project] Henrik should we include Settings-Sound ?

by Henrik Sperre Johansen

On 24.04.2011 15:57, Mariano Martinez Peck wrote: > I saw that package in PharoSound and I wonder if it should be added to > the Metacello conf > > cheers > > > -- > Mariano > http://marianopeck.wordpress.com > Yes, in a version 4.0 for 1.1 and 1.3 together with Sound-MarianoMartinezPeck.65 , as soon as we revert some stuff that was done in base which broke it. IE. change registration back to working with instances, and soundEnabled to use a class var of SoundService rather than that of it's registered class. It will not work with the code based on branch from PharoTaskForces (Sound-MarianoMartinezPeck.64), as that one just deleted all preferences rather than preserve them in a functionally correct way. Cheers, Henry

April 26, 2011

Re: [Pharo-project] Why we have Behavior >> flushCache?

by Alexandre Bergel

Not using the receiver is indeed misleading. I thought it simply flushes the cache for a particular class Alexandre On 26 Apr 2011, at 06:34, Mariano Martinez Peck wrote: > Hi. As far as I can see, > > Behavior >> flushCache > "Tell the interpreter to remove the contents of its method lookup cache, if it has > one. Essential. See Object documentation whatIsAPrimitive." > > <primitive: 89> > self primitiveFailed > > > And primitive 89 does nothing in particular with the receiver (the class in this case). In both, InterpreterVM and Cog, the WHOLE cache is flushed, there is NOTHING related to the receiver class. Of course, that's at least what it looks for me (please tell me if I am wrong). > So...if this is the case, wouldn't make sense to move it elsewhere? like Smalltalk flushCache or Smalltalk vm flushCache (and it is a good moment to reify the VM). So after we can do: Smalltalk vm version. Smalltlak vm flushCache, Smalltalk vm parameterAt: , etc.... > > If you don't like doing "Smalltalk vm" then we can create a VM class with all class methods, or a singleton and use #current or a singleton and put it in Smalltalk globals...etc > > We will need to fix a couple of senders, thus. > > What do you think? For me is really confusing, and you don't understand it until you see the primitive implementation. > > Cheers > > -- > Mariano > http://marianopeck.wordpress.com > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 26, 2011