- Pharo-dev - lists.pharo.org

[Pharo-project] why #ifNotNil: accepts parameter?
by Esteban Lorenzano Jan. 29, 2009

Jan. 29, 2009

Hi, I'm trying to understand why pharo modifies squeak behavior of ifNotNil: and introduces the optional parameter... is there a reason? Cheers, Esteban

6 10

[Pharo-project] Fwd: [tous-lil] [Fwd: ArrÃªtprolongÃ© de InriaGforge]
by Alexandre Bergel Jan. 28, 2009

Jan. 28, 2009

gforge is down for now :-( Alexandre Begin forwarded message: > From: minvielle <arnaud.minvielle(a)inria.fr> > Date: 28 January 2009 16:58:51 CEST > To: tous-lil(a)inria.fr > Subject: [tous-lil] [Fwd: ArrÃªtprolongÃ© de InriaGforge] > Reply-To: tous-lil-owner(a)inria.fr > > Suite Ã une dÃ©faillance matÃ©rielle, la forge INRIA est actuellement > indisponible. La livraison des nouveaux composants prÃ©vue ce matin > est retardÃ©e, celle-ci est prÃ©vue cette aprÃ¨s-midi pour 16H. > > Nous vous tiendrons informÃ©s des Ã©volutions. > Nous vous remercions Ã l'avance pour votre comprÃ©hension, > > L'Ã©quipe transversale INRIAGForge. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 1

[Pharo-project] Fwd: [tous-lil] [Fwd: ArrÃªtprolongÃ© de InriaGforge]
by Alexandre Bergel Jan. 28, 2009

Jan. 28, 2009

gforge is down for now :-( Alexandre Begin forwarded message: > From: minvielle <arnaud.minvielle(a)inria.fr> > Date: 28 January 2009 16:58:51 CEST > To: tous-lil(a)inria.fr > Subject: [tous-lil] [Fwd: ArrÃªtprolongÃ© de InriaGforge] > Reply-To: tous-lil-owner(a)inria.fr > > Suite Ã une dÃ©faillance matÃ©rielle, la forge INRIA est actuellement > indisponible. La livraison des nouveaux composants prÃ©vue ce matin > est retardÃ©e, celle-ci est prÃ©vue cette aprÃ¨s-midi pour 16H. > > Nous vous tiendrons informÃ©s des Ã©volutions. > Nous vous remercions Ã l'avance pour votre comprÃ©hension, > > L'Ã©quipe transversale INRIAGForge. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

[Pharo-project] New pharo dev
by Damien Cassou Jan. 27, 2009

Jan. 27, 2009

Based on 10213: https://gforge.inria.fr/frs/download.php/16049/pharo0.1-10213dev09.01.3.zip -- Damien Cassou http://damiencassou.seasidehosting.st

1 0

[Pharo-project] Writing a conditions for breakpoint
by Igor Stasenko Jan. 27, 2009

Jan. 27, 2009

suppose, you have a method, say foo: bar baz: zork and want to set a conditional breakpoint for it.. a most easy way to provide a condition is to ask user for providing a block like: [:receiver :arguments :context | " .... return true to break " ] but more convenient would be to ask user to write a condition as a method: foo: bar baz: zork "put your condition code here" ^ bar == 0 "break if bar is zero" then user naturally would access interesting things w/o need to deal with block-like constructs, where arguments is accessible but in inconvenient manner i.e. type 'bar' instead of 'arguments at: 1' This is very good, except one thing, which i worry about: what if i want to write a condition which needs to test a specific context state. I can freely pass a context in a block, but can't pass it in method , because 'condition' method selector should be same as selector where breakpoint will be installed to. What you think would be better? Or maybe i should let users decide , what is best for them? So, they can write conditions using both forms - as a block closure or as method? -- Best regards, Igor Stasenko AKA sig.

4 9

[Pharo-project] Issue 465 - Pharo dev
by Francois Stephany Jan. 26, 2009

Jan. 26, 2009

Hi, Small bug found in Pharo-dev in OTToolset class. See issue 465. Cheers, Francois [Thanks to David]

3 2

[Pharo-project] Fwd: [INRIAGforge] 27-28 Jan 2009 : Scheduled dowtime
by StÃ©phane Ducasse Jan. 26, 2009

Jan. 26, 2009

Begin forwarded message: > From: <noreply(a)gforge.inria.fr> > Date: January 26, 2009 6:30:19 PM CEST > To: stephane.ducasse(a)inria.fr > Subject: [INRIAGforge] 27-28 Jan 2009 : Scheduled dowtime > > On January 27th 2009, from 7h00pm to 8h00pm and January 28th > 2009,from 6h00am to 8h00am, the site and all associated services > will be unavailable due to maintenance operations on servers and > networks by Renater. > A reply to this announce will signal the end of the maintenance. > We apologize for any inconvenience. > Cordially > The InriaGforge Team >

1 0

Jan. 26, 2009

Begin forwarded message: > From: John M McIntosh <johnmci(a)smalltalkconsulting.com> > Date: January 26, 2009 7:30:23 PM CEST > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Re: [Pharo-project] Process stuck in 10156+OB? > Reply-To: johnmci(a)smalltalkconsulting.com > > Ok, I think the test is attached, however you should change the name > from JMMTest to something else. > > like MacHostMenusTestCaseCharacterSubstitutions > > > On 20-Nov-08, at 1:27 PM, StÃ©phane Ducasse wrote: > > >> john do you have a new version of the package since >> the method calculateShouldBeFrom:using: is missing >> >> On Nov 20, 2008, at 12:03 AM, John M McIntosh wrote: >> >>> testCharacterChanging >>> | testString item shouldBe resultingString where | >>> #(';' '^' '!' '<' '/' '(' ) >>> do: [:c | #('*' '* ' '* ' '**' '** ' '** ' >>> ')' '*)' '* )' '* )' '**)' '** )' '** )' >>> ')' '*)' '*X)' '*XX)' '**)' '**X)' '**XX)' >>> '))' '*))' '*X))' '*XX))' '**))' '**X))' '**XX))' >>> '(' '*(' '*X(' '*XX(' '**)' '**X(' '**XX(' >>> '((' '*((' '*X((' '*XX((' '**((' '**X((' '**XX((' >>> ) >>> do: [:template | >>> testString := template copyReplaceAll: '*' with: c. >>> testString >>> permutationsDo: [:mixedUp | >>> item := mixedUp copy. >>> shouldBe := self calculateShouldBeFrom: item using: c. >>> resultingString := self modifySqueakMenu: item copy. >>> self should: [shouldBe = resultingString]. >>> (where := resultingString indexOf: $/) > 0 >>> ifTrue: [self should: [(mixedUp at: where) = $(]. >>> self should: [(mixedUp at: where+2) = $)]. >>> self should: [(mixedUp at: where+1) asUppercase = >>> (resultingString at: where+1)]]]]] >> > > -- > = > = > = > = > = > ====================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> > Corporate Smalltalk Consulting Ltd. http:// > www.smalltalkconsulting.com > = > = > = > = > = > ====================================================================== > >

1 0

[Pharo-project] Added Class>>subclass: and Class>>subclass:instanceVariableNames:
by Alexandre Bergel Jan. 26, 2009

Jan. 26, 2009

I always missed these two methods. Class has been extended with these two methods. A new version of Kernel has been saved in PharoInbox (version 253). Note that it has been merged with Kernel- adrian_lienhard.252 http://code.google.com/p/pharo/issues/detail?id=464 Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

[Pharo-project] Smalltalk condenseChanges broken?
by John M McIntosh Jan. 26, 2009

Jan. 26, 2009

Well I'm fairly sure that I downloaded a Pharo0.1Core-10204.image then did a "Smalltalk condenseChanges" then an extended search for 'foobar' and walkback time, the changes file is messed up. at TraitBehavior class>>sourceCodeAt: where selector is noteChangedSelectors: However if someone can cross check for me, that would be helpful. -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

3 2