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

Re: [Pharo-project] Maybe a brain dead idea

by merlyn＠stonehenge.com

>>>>> "Friedrich" == Friedrich Dominicus <frido(a)q-software-solutions.de> writes: Friedrich> I have searched for a way to generate accessor functions with a program, Friedrich> but did not understand the implementaion on Pharo but I've stolen Friedrich> something from Gemstone Smalltalk (if that is not ok, would someone Friedrich> please be so kind to tell me) and there is a method Why would you want accessors for *all* your instance variables? Methods provide the public interface for a class's objects. An object that is just a bag of bits such that any other object can get or set every one of its instance variables is better represented as a Dictionary. You should design your object's interface respecting the needed protocols, not its internal design. Bad code smell otherwise. -- Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095 <merlyn(a)stonehenge.com> <URL:http://www.stonehenge.com/merlyn/> Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc. See http://methodsandmessages.posterous.com/ for Smalltalk discussion

July 26, 2011

Re: [Pharo-project] problem with text editor when editing code and get a proposal to change it

by Gary Chambers

Lol, that was quite lame! (Guessing that save of method not doing the source code after prompt... there is an issue for that I think) Regards, Gary ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, July 26, 2011 2:58 PM Subject: Re: [Pharo-project] problem with text editor when editing code and get a proposal to change it On 26 July 2011 15:51, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > In 1.4 I get an annoying regression, when the system propose me a change > my text gets mangled or not updated. > Am I the only one to get that? > It would be good to fix that. > We only accept a good bug reports (with video coverage!) :) > Stef -- Best regards, Igor Stasenko AKA sig.

July 26, 2011

Re: [Pharo-project] Maybe a brain dead idea

by Igor Stasenko

On 26 July 2011 17:27, Friedrich Dominicus <frido(a)q-software-solutions.de> wrote: > or maybe not. > > I have searched for a way to generate accessor functions with a program, > but did not understand the implementaion on Pharo but I've stolen > something from Gemstone Smalltalk (if that is not ok, would someone > please be so kind to tell me) and there is a method > compileMissingAccessingMethods > > and here it is: > compileMissingAccessingMethods > > "Creates accessing and updating methods for all instance variables that do not > Â already have such methods." > > Maybe I was just to stupid Â to find the according function in Pharo, > however this stuff seems to do Â what I wanted it do do. > > If someone has a better idea or just tell me the function of it in > Pharo, well then please do so. > Yes, see the #createInstVarAccessors method implementation in Browser. I think you can stole it from there and rewrite for own needs :) > Regards > Friedrich -- Best regards, Igor Stasenko AKA sig.

July 26, 2011

[Pharo-project] Maybe a brain dead idea

by Friedrich Dominicus

or maybe not. I have searched for a way to generate accessor functions with a program, but did not understand the implementaion on Pharo but I've stolen something from Gemstone Smalltalk (if that is not ok, would someone please be so kind to tell me) and there is a method compileMissingAccessingMethods and here it is: compileMissingAccessingMethods "Creates accessing and updating methods for all instance variables that do not already have such methods." | argName newLine allVarNames varNames sel | argName := 'newValue'. allVarNames := self allInstVarNames. [allVarNames includes: argName] whileTrue: [ argName := 'z' , argName. ]. newLine:= Character lf asString. varNames := self instVarNames. varNames do: [ :var | (self includesSelector: var ) ifFalse: [ self class compile: (var , newLine , newLine , ' "Return the value of the instance variable ''' , var , '''."' , newLine , ' ^' , var , newLine). ]. sel := var, ($: asString). (self includesSelector: sel) ifFalse: [ self compile: (sel, argName , newLine , newLine , ' "Modify the value of the instance variable ''' , var , '''."' , newLine , ' ' , var , ' := ' , argName , newLine). ] ] Maybe I was just to stupid to find the according function in Pharo, however this stuff seems to do what I wanted it do do. If someone has a better idea or just tell me the function of it in Pharo, well then please do so. Regards Friedrich

July 26, 2011

[Pharo-project] DNU with beMethodArg?

by StÃ©phane Ducasse

Hi guys I was debugging some bug and I got the following DoItIn: ThisContext ^ self do: [:each | ((ThisContext namedTempAt: 1) includes: each) ifFalse: [^ false]] I selected (ThisContext namedTempAt: 1 and I got MessageAsTempNode does not understand beMethodArg method: doit context: ctxt " pattern [ | temporaries ] block => MethodNode." | sap blk prim temps messageComment methodNode | properties := AdditionalMethodState new. sap := self pattern: doit inContext: ctxt. "sap={selector, arguments, precedence}" properties selector: (sap at: 1). encoder selector: (sap at: 1). (sap at: 2) do: [:argNode | argNode beMethodArg]. ^^^^ doit ifFalse: [self pragmaSequence]. temps := self temporaries. messageComment := currentComment. currentComment := nil. doit ifFalse: [self pragmaSequence]. prim := self pragmaPrimitives. self statements: #() innerBlock: doit. blk := parseNode. doit ifTrue: [blk returnLast] ifFalse: [blk returnSelfIfNoOther: encoder]. hereType == #doIt ifFalse: [^self expected: 'Nothing more']. self interactive ifTrue: [self removeUnusedTemps]. methodNode := self newMethodNode comment: messageComment. ^methodNode selector: (sap at: 1) arguments: (sap at: 2) precedence: (sap at: 3) temporaries: temps block: blk encoder: encoder primitive: prim properties: properties argNode is a MessageAsTempNode and beMethodArg is only defined on TempVariableNode http://code.google.com/p/pharo/issues/detail?id=4551 Stef

July 26, 2011

Re: [Pharo-project] problem with text editor when editing code and get a proposal to change it

by Igor Stasenko

On 26 July 2011 15:51, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > In 1.4 I get an annoying regression, when the system propose me a change my text gets mangled or not updated. > Am I the only one to get that? > It would be good to fix that. > We only accept a good bug reports (with video coverage!) :) > Stef -- Best regards, Igor Stasenko AKA sig.

July 26, 2011

[Pharo-project] problem with text editor when editing code and get a proposal to change it

by StÃ©phane Ducasse

Hi guys In 1.4 I get an annoying regression, when the system propose me a change my text gets mangled or not updated. Am I the only one to get that? It would be good to fix that. Stef

July 26, 2011

Re: [Pharo-project] [update 1.4] #14060

by Damien Cassou

Is it now possible to browse Smalltalk class/packages/methods/categories using Ring? Said differently, how can I instanciate Ring on the image? On Tue, Jul 26, 2011 at 3:42 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > 14060 > ----- > > - enhancing Ring and fixing some API for better tools integration. SystemNavigation is now using Ring objects. > todo: should fix some tests on unsentMessages > > Stef and Veronica > -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 26, 2011

[Pharo-project] [update 1.4] #14060

by StÃ©phane Ducasse

14060 ----- - enhancing Ring and fixing some API for better tools integration. SystemNavigation is now using Ring objects. todo: should fix some tests on unsentMessages Stef and Veronica

July 26, 2011

Re: [Pharo-project] Pharo 1.3 Seaside 'client' build ?

by Marcus Denker

On Jul 25, 2011, at 4:31 PM, Sven Van Caekenberghe wrote: > Hi (Marcus), > > I was looking for a Pharo 1.3 Seaside 'client' build on the CI server(s) but couldn't find it. > > It used to be available for 1.2.x (this seems to be gone as well). > > I think that for good reciprocal relations with Seaside, it would be very good to have a tested build of the current main Pharo images. It make a good testcase as well. And it saves quite some work, loading the Seaside config is pretty slow. > > I remember reading something about some clients being removed from the CI's, but I didn't register it fully. > Yes, I will add that to the new Jenkis setup asap. (some of the next days). > Thx, > > Sven > > PS: Another questions is: is 1.3 'released', if so where are the links on the website, where is the 'noise' ? We should fix the last open reports, create a new one-click and do the releaseâ¦ http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3 -- Marcus Denker Do it together: http://taskfor.us

July 26, 2011