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

[Pharo-project] Shout-Examples are cool :)

by StÃ©phane Ducasse

Hi everybody Alain did a good job to describe four nice example of how to use Shout. Finally we get some examples we can learn from. The examples are in Shout-Examples category. Stef

Oct. 17, 2011

Re: [Pharo-project] Can this be improved in Glamourous?

by StÃ©phane Ducasse

good I will try it. On Oct 17, 2011, at 8:33 AM, Marcus Denker wrote: > > On Oct 16, 2011, at 11:14 PM, StÃ©phane Ducasse wrote: > >>> We need to fix the Metacello of Shout to load the latest version so we can build a Full image based >>> on 13315, this should solve some of the problems. >> >> I published a new configurationOfShout load for 1.3 the latest version published by alain. >> Now I'm sick so I will sleep. >> > > I have started a build of 1.3 Full: > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/ > > > > -- > Marcus Denker -- http://marcusdenker.de > >

Oct. 17, 2011

Re: [Pharo-project] Can this be improved in Glamourous?

by Marcus Denker

On Oct 16, 2011, at 11:14 PM, StÃ©phane Ducasse wrote: >> We need to fix the Metacello of Shout to load the latest version so we can build a Full image based >> on 13315, this should solve some of the problems. > > I published a new configurationOfShout load for 1.3 the latest version published by alain. > Now I'm sick so I will sleep. > I have started a build of 1.3 Full: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/ -- Marcus Denker -- http://marcusdenker.de

Oct. 17, 2011

Re: [Pharo-project] Can this be improved in Glamourous?

by StÃ©phane Ducasse

> We need to fix the Metacello of Shout to load the latest version so we can build a Full image based > on 13315, this should solve some of the problems. I published a new configurationOfShout load for 1.3 the latest version published by alain. Now I'm sick so I will sleep. Stef

Oct. 16, 2011

Re: [Pharo-project] Can this be improved in Glamourous?

by StÃ©phane Ducasse

ConfigurationOfPharo should load 1.7 I do not understand how we can say that it should load a stable version because we will get 1.7 automatically. Mariano do you have an idea? Right now we have project: 'RefactoringBrowser' with: '1.6'; project: 'RefactoringBrowser Tests' with: '1.6'; version13beta2: spec <version: '1.3-beta2' imports: #('1.3-baseline')> spec for: #common do: [ spec blessing: #development. spec author: 'Mariano Martinez Peck'. spec description: 'Version for pharo 1.3 dev'. ]. spec for: #pharo do: [ spec package: 'Shortcuts-Help' with: 'Shortcuts-Help-LaurentLaffont.2'; package: 'Smalltalk-Help' with: 'Smalltalk-Help-tbn.2'; package: 'RoelTyper' with: 'RoelTyper-FredericPluquet.82'; package: 'ImageForDevelopers' with: 'ImageForDevelopers-pharo-MarianoMartinezPeck.263'; package: 'Pharo-Project-Help' with: 'Pharo-Project-Help-tbn.10'; package: 'Metacello-Help' with: 'Metacello-Help-DaleHenrichs.9'. spec project: 'Autotest' with: '1.1'; project: 'Autotest Help Tests' with: '1.1'; project: 'MemoryMonitor' with: '1.0.3'; project: 'PharoNonCorePackages' with: '1.3'; project: 'Shout' with: '1.3'; project: 'Shout Tests' with: '1.3'; project: 'OCompletion' with: '1.4'; project: 'OCompletion Tests' with: '1.4'; project: 'OB Dev' with: '1.3'; project: 'OB Dev Tests' with: '1.3'; project: 'AutomaticMethodCategorizer' with: '1.3'; project: 'RefactoringBrowser' with: '1.6'; project: 'RefactoringBrowser Tests' with: '1.6'; project: 'ProfStef' with: '1.7'; project: 'ProfStef Tests' with: '1.7'; project: 'ScriptManager' with: '1.3']

Oct. 16, 2011

Re: [Pharo-project] Can this be improved in Glamourous?

by StÃ©phane Ducasse

People should tell me what is not working because do me it is working. I spent time merging your changes and updating the configurationOfRefactoringBrowser. > There is kind of a mess for 1.3: > > There are various ambiguous versions of OB, Shout and eCompletion > floating around that break some parts of the system, because of the > text editor changes. > > Also there are also various versions of RB that do not work in 1.3, > because of the changes in 1.4. My version does not load the change in 1.4. > I've been building 1.3 images for a while, so you "just" have to take > the same versions to get a working image. > This seems to be the case for AST and Refactoring that were posted above. ??? For me I want a configurationOfXXX working. the one I did is working or people should tell me why it is not. Stef

Oct. 16, 2011

Re: [Pharo-project] Fwd: trying to understand loops in pharo

by StÃ©phane Ducasse

On Oct 16, 2011, at 10:33 PM, Nicolas Cellier wrote: > Ah, I see, this sound appealing. > But I would object this: (I'm speaking of do:, not only to:do:) > 1) what the last value mean for unordered collections? > 2) for a SequenceableCollection, the behavior is already > (someCollection inject: nil into: [:void :each | aBlock value: each]) > 3) returning the last value in all implementors of #do: would cost > complexification of code and possibly slow down (non clean blocks) > > Is it really useful? Not really I do not like the idea to rely on it. but in that case the code you be explicit #undefined/nil should be the last expression of the block. My point was: the semantics of a block is to return the last expression and we should be consistent with that. Stef > > Nicolas > > 2011/10/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> for me the last expression of the block. >> >> Stef >>>>> Which return value would be useful? >>>> >>>> That's not the right question. IMO the compiler should answer the same >>>> result as the non-inlined one when the return value is asked for. Arguably >>>> the non-inline version needs to be commented to specify that it returns the >>>> value it does (in this case self), and that the compiler's optimiser >>>> reflects this. >>>> >>> >>> Agree, but I was wondering what useful object this common answer could be? >>> >>>>> >>>>> Nicolas >>>>> >>>>> 2011/10/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>>>> A friend of mine ask me the following >>>>>> >>>>>> |result| >>>>>> result := String new. >>>>>> 1 to: 10 do: [:n | result := result, n printString, ' ']. >>>>>> I am trying to do or print this code. It prints 'nil' instead of a >>>>>> collection. Its an example from PBE book. >>>>>> do you know the reason? >>>>>> although this one's working: >>>>>> result := String new. >>>>>> (1 to: 10) do: [:n | result := result, n printString, ' ']. >>>>>> >>>>>> I checked the implementation >>>>>> Interval>>do: aBlock >>>>>> "Evaluate aBlock for each value of the interval. >>>>>> Implementation note: instead of repeatedly incrementing the value >>>>>> aValue := aValue + step. >>>>>> until stop is reached, >>>>>> We prefer to recompute value from start >>>>>> aValue := start + (index * step). >>>>>> This is better for floating points accuracy, while not degrading Integer >>>>>> and >>>>>> Fraction speed too much. >>>>>> Moreover, this is consistent with methods #at: and #size" >>>>>> | aValue index size | >>>>>> index := 0. >>>>>> size := self size. >>>>>> [index < size] >>>>>> whileTrue: [aValue := start + (index * step). >>>>>> index := index + 1. >>>>>> aBlock value: aValue] >>>>>> >>>>>> Number>>to: stop do: aBlock >>>>>> "Normally compiled in-line, and therefore not overridable. >>>>>> Evaluate aBlock for each element of the interval (self to: stop by: 1)." >>>>>> | nextValue | >>>>>> nextValue := self. >>>>>> [nextValue <= stop] >>>>>> whileTrue: >>>>>> [aBlock value: nextValue. >>>>>> nextValue := nextValue + 1] >>>>>> >>>>>> any further idea than := value is different from value: >>>>>> Stef >>>>> >>>> >>>> >>>> >>>> -- >>>> best, >>>> Eliot >>>> >>> >> >> >> >

Oct. 16, 2011

Re: [Pharo-project] Can this be improved in Glamourous?

by Lukas Renggli

There is kind of a mess for 1.3: There are various ambiguous versions of OB, Shout and eCompletion floating around that break some parts of the system, because of the text editor changes. Also there are also various versions of RB that do not work in 1.3, because of the changes in 1.4. I've been building 1.3 images for a while, so you "just" have to take the same versions to get a working image. This seems to be the case for AST and Refactoring that were posted above. Lukas On 16 October 2011 22:35, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Now for Shout marcus what is the problem? > What is left to do to release fully 1.3? > > Because I will do it and this is done. > We cannot stay like that forever. > > Stef > > > On Oct 16, 2011, at 10:24 PM, Marcus Denker wrote: > >> >> On Oct 16, 2011, at 10:07 PM, Tudor Girba wrote: >> >>> Hi, >>> >>> If you give me the script, I build one based on the Core. >>> >> >> Husdon does: >> >> Gofer new >> squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfPharo'; >> load. >> >> >> -- >> Marcus Denker -- http://marcusdenker.de >> >> > > > -- Lukas Renggli www.lukas-renggli.ch

Oct. 16, 2011

Re: [Pharo-project] External arrays (DWORD, DOUBLE, etc.)

by Nicolas Cellier

2011/10/16 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: > Hello all, > > I have some classes that started out as place holders to allow me to load code I wrote for Dolphin, and over time, have become almost useful :) Â One thing I really needed was a contiguous array of doubles; there is a LOT of code that uses them. Â Enter ExternalArray with many subclasses, most of which translate #at: and #at:put: into appropriate methods of ByteArray (#doubleAt:put:, etc.). > > The numbers end up being stored in a byte array, so the indexing looks at position and element size. Â Access is very slow, but most of the time, I simply allocate a block of memory (e.g. create a byte array, which is fast) and then pass it to an external C/C++ function to do the real work. > > The passing is the subject of this message. Â I end up (for FFI) describing the arguments as void*, passing the byte array to the function. Â Is there a way to tell FFI that an instance of DOUBLEArray can be treated as a double*? > > Bill > > > > Just a warning: beware of alignment. ByteArray are 4-byte aligned, some libraries might require double * to be 8-byte aligned. See http://smallissimo.blogspot.com/2011/08/smallapack-progress-on-squeak.html Otherwise, there is no problem for declaring a double * or a float *, see how it is used in http://www.squeaksource.com/Smallapack The problem I did not resolve is to pass an array of structures other than with void *... Nicolas

Oct. 16, 2011

Re: [Pharo-project] Can this be improved in Glamourous?

by StÃ©phane Ducasse

Now for Shout marcus what is the problem? What is left to do to release fully 1.3? Because I will do it and this is done. We cannot stay like that forever. Stef On Oct 16, 2011, at 10:24 PM, Marcus Denker wrote: > > On Oct 16, 2011, at 10:07 PM, Tudor Girba wrote: > >> Hi, >> >> If you give me the script, I build one based on the Core. >> > > Husdon does: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfPharo'; > load. > > > -- > Marcus Denker -- http://marcusdenker.de > >

Oct. 16, 2011