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

[Pharo-project] I am petrified. I don't know what to say ........... (just look at that)

by Igor Stasenko

DiskProxy>>comeFullyUpOnReload: smartRefStream "Internalize myself into a fully alive object after raw loading from a DataStream. (See my class comment.) DataStream will substitute the object from this eval for the DiskProxy." | globalObj symbol arrayIndex | symbol := globalObjectName. "See if class is mapped to another name" (smartRefStream respondsTo: #renamed) ifTrue: [ "If in outPointers in an ImageSegment, remember original class name. See mapClass:installIn:. Would be lost otherwise." >>>>> (thisContext sender sender sender sender sender sender sender sender receiver class == ImageSegment >>>>> and: [ thisContext sender sender sender sender method == (DataStream compiledMethodAt: #readArray) ]) ifTrue: [ arrayIndex := thisContext sender sender sender sender tempAt: 4. "index var in readArray. Later safer to find i on stack of context." smartRefStream renamedConv at: arrayIndex put: symbol ]. "save original name" symbol := smartRefStream renamed at: symbol ifAbsent: [ symbol ] ]. "map" globalObj := Smalltalk globals at: symbol ifAbsent: [ preSelector == nil & (constructorSelector = #yourself) ifTrue: [ Transcript cr; show: symbol , ' is undeclared.'. (Undeclared includesKey: symbol) ifTrue: [ ^ Undeclared at: symbol ]. Undeclared at: symbol put: nil. ^ nil ]. ^ self error: 'Global "' , symbol , '" not found' ]. preSelector ifNotNil: [ Symbol hasInterned: preSelector ifTrue: [ :selector | [ globalObj := globalObj perform: selector ] on: Error do: [ :ex | ex messageText = 'key not found' ifTrue: [ ^ nil ]. ^ ex signal ] ] ]. "keep the Proxy if Project does not exist" constructorSelector ifNil: [ ^ globalObj ]. Symbol hasInterned: constructorSelector ifTrue: [ :selector | [ ^ globalObj perform: selector withArguments: constructorArgs ] on: Error do: [ :ex | ex messageText = 'key not found' ifTrue: [ ^ nil ]. ^ ex signal ] ]. "args not checked against Renamed" ^ nil -- Best regards, Igor Stasenko AKA sig.

Aug. 12, 2011

Re: [Pharo-project] some explanations about what we are doing :)

by Henrik Johansen

On 12. aug. 2011, at 15:15, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > hi guys > > Context: > So let us face it our attempt to manage a core and another image did not work well. After RPackage I will focus on a process (based on metacello) where > we take a core + a spec + fixes and it produces a new core + a new spec + a new set of packages. But I need time to do that. > > Actions: > So now we are including several packages in the image so that we do not have two images. > FS > RB engine > Shout > OCompletion > Collection-Arithmetics > SystemAnnouncement > this one is special and some of you may not know it. > It is a package that raise announcement for system changes. > The idea is that we will then > 1- change all the tools to register to SystemAnnouncement > 2- replace all the SystemChangeNotification hooks by SystemAnnouncement > 3- remove our old friend SystemChangeNotifier. > > The idea is then to be able to integrate/enhance these packages deeper into the system > FS for example to replace the old file package > > Stef, Marcus, Igor, Luc, Nick sprinting on a sunday day (yes it happens here too). > > Ugh. Collection-Aritmetics was extracted exactly -because- it's nothing that belongs in image by default... As for RB, my impression through your conversations with Lukas is that it's not enough to include it, you need someone who understands the architecture for bug fixes/changes that preserve architectural integrity rather than end up as ugly hacks. I like the functionality of OCompletion, but from what little I've read of Shout, only it's mother could love it. (same applies to texteditor etc. though, so I guess it's not a very good argument against integrating it) FS + SystemAnnouncements, I'm all for :) Cheers, Henry

Aug. 12, 2011

[Pharo-project] [update 1.4] #14086

by Marcus Denker

14086 ----- Issue 4621: ToolRegistery bug http://code.google.com/p/pharo/issues/detail?id=4621 Issue 4610: MCWorkingCopyBrowser references lot of undefined variables http://code.google.com/p/pharo/issues/detail?id=4610 -- Marcus Denker -- http://marcusdenker.de

Aug. 12, 2011

Re: [Pharo-project] Bug in parsing numbers in PPSmalltalkGrammar?

by Damien Pollet

On 12 August 2011 13:12, Lukas Renggli <renggli(a)gmail.com> wrote: > Ideally we should probably implement the number parsing in > PetitParser. Maybe as a separate parser that can be used in > PPSmalltalkGrammar? Yes, there is a need for reusable parsers for all these things with pretty standard syntaxes: numbers, URLs, emails, dates/timestampsâ¦ -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Aug. 12, 2011

[Pharo-project] [update 1.4] #14085

by Marcus Denker

14085 ----- Issue 4587: Failing tests related to renaming classes http://code.google.com/p/pharo/issues/detail?id=4587 -- Marcus Denker -- http://marcusdenker.de

Aug. 12, 2011

Re: [Pharo-project] PPElementParser & a small PetitTests contribution

by Damien Pollet

On 12 August 2011 07:21, Lukas Renggli <renggli(a)gmail.com> wrote: > Do you have a ready made-image somewhere? I don't understand it from > reading your mail only. Yup, get Pharo Coral from Jenkins: https://ci.lille.inria.fr/pharo/job/Pharo%20Coral/ -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Aug. 12, 2011

Re: [Pharo-project] formatting style

by Lukas Renggli

On 12 August 2011 15:42, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I mean that I prefer > >>> Smalltalk tools >>> Â Â Â Â Â Â Â Â register: ;lkl;k;lk;l >>> Â Â Â Â Â Â Â Â in: lkl;k;lkl;kl; > > over > >>> Smalltalk tools register: ;lkl;k;lk;l >>> Â Â Â Â Â Â Â Â in: lkl;k;lkl;kl; > > > because I do not see fast that the message is register: in: Hmm, I still don't understand your example because the $; has semantic meaning and because the example doesn't even compile :-) > and I guess that you are formatting the way I like but the rb formatter may be wrong because You can configure after how how many keyword parts (that is probably too low right now) it should print on one line. Also you can tell it how many characters per line you maximally want (used to be 80, I think i changed the default to 100; but probably should be inifite). Lukas > > On Aug 12, 2011, at 1:49 PM, Lukas Renggli wrote: > >> Hmm, I don't get your example. >> >> What I changed is that the formatter does not enforce the useless >> parenthesis around the receiver of a cascade. Can be disabled though. >> >> Also note that there are settings to automatically format code on >> display and/or accept. I use the "on display" mode often to read ugly >> code :-) >> >> Lukas >> >> On 12 August 2011 13:29, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> Yes >>> >>> Â Â Â Â Smalltalk tools >>> Â Â Â Â Â Â Â Â register: ;lkl;k;lk;l >>> Â Â Â Â Â Â Â Â in: lkl;k;lkl;kl; >>> >>> >>> stef >>> On Aug 12, 2011, at 1:20 PM, Lukas Renggli wrote: >>> >>>>> I always think of this a the Seaside style, but I am not sure if that is a correct attribution. >>>> >>>> Haha, thank you. >>>> >>>> Actually the refactoring browser formatter with the default settings >>>> is quite close to the Seaside style, I just recently submitted some >>>> fixes for cascades. The only thing that I don't like about the >>>> automatic formatter is how the brackets in multiline blocks are >>>> aligned. Anyway, the formatter would style #inject:into: as you >>>> suggest. >>>> >>>> Lukas >>>> >>>> -- >>>> Lukas Renggli >>>> www.lukas-renggli.ch >>>> >>> >>> >>> >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > > -- Lukas Renggli www.lukas-renggli.ch

Aug. 12, 2011

Re: [Pharo-project] ring new version question

by Veronica Isabel Uquillas Gomez

Hi C, I will make a webpage for ring asap... Veronica On 12 Aug 2011, at 15:23, Craig Latta wrote: > > Hi Veronica-- > > Is there a Ring website with an overview? > > > thanks! > > -C > > -- > Craig Latta > www.netjam.org/resume > +31 6 2757 7177 > + 1 415 287 3547 > > >

Aug. 12, 2011

Re: [Pharo-project] some explanations about what we are doing :)

by StÃ©phane Ducasse

On Aug 12, 2011, at 3:21 PM, Mariano Martinez Peck wrote: > > > On Fri, Aug 12, 2011 at 3:15 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > hi guys > > Context: > So let us face it our attempt to manage a core and another image did not work well. After RPackage I will focus on a process (based on metacello) where > we take a core + a spec + fixes and it produces a new core + a new spec + a new set of packages. But I need time to do that. > > Actions: > So now we are including several packages in the image so that we do not have two images. > > I am not against this, but I think it is a must to provide a #shrinkToPharoCore and a hudson associated to that. yes good idea even if for FS and SystemAnnouncement will be inside the core. > > > > FS > RB engine > Shout > OCompletion > Collection-Arithmetics > SystemAnnouncement > this one is special and some of you may not know it. > It is a package that raise announcement for system changes. > The idea is that we will then > 1- change all the tools to register to SystemAnnouncement > 2- replace all the SystemChangeNotification hooks by SystemAnnouncement > 3- remove our old friend SystemChangeNotifier. > > The idea is then to be able to integrate/enhance these packages deeper into the system > FS for example to replace the old file package > > Stef, Marcus, Igor, Luc, Nick sprinting on a sunday day (yes it happens here too). > > > > > > -- > Mariano > http://marianopeck.wordpress.com >

Aug. 12, 2011

Re: [Pharo-project] formatting style

by StÃ©phane Ducasse

I mean that I prefer >> Smalltalk tools >> register: ;lkl;k;lk;l >> in: lkl;k;lkl;kl; over >> Smalltalk tools register: ;lkl;k;lk;l >> in: lkl;k;lkl;kl; because I do not see fast that the message is register: in: and I guess that you are formatting the way I like but the rb formatter may be wrong because > > Smalltalk tools > register: ;lkl;k;lk;l should be more > > Smalltalk tools register: ;lkl;k;lk;l On Aug 12, 2011, at 1:49 PM, Lukas Renggli wrote: > Hmm, I don't get your example. > > What I changed is that the formatter does not enforce the useless > parenthesis around the receiver of a cascade. Can be disabled though. > > Also note that there are settings to automatically format code on > display and/or accept. I use the "on display" mode often to read ugly > code :-) > > Lukas > > On 12 August 2011 13:29, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> Yes >> >> Smalltalk tools >> register: ;lkl;k;lk;l >> in: lkl;k;lkl;kl; >> >> >> stef >> On Aug 12, 2011, at 1:20 PM, Lukas Renggli wrote: >> >>>> I always think of this a the Seaside style, but I am not sure if that is a correct attribution. >>> >>> Haha, thank you. >>> >>> Actually the refactoring browser formatter with the default settings >>> is quite close to the Seaside style, I just recently submitted some >>> fixes for cascades. The only thing that I don't like about the >>> automatic formatter is how the brackets in multiline blocks are >>> aligned. Anyway, the formatter would style #inject:into: as you >>> suggest. >>> >>> Lukas >>> >>> -- >>> Lukas Renggli >>> www.lukas-renggli.ch >>> >> >> >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch >

Aug. 12, 2011