- Pharo-dev - lists.pharo.org

[Pharo-project] Performance in Workspace
by Robert Kovacic Oct. 6, 2009

Oct. 6, 2009

I have installed setup_pharo1.0-10466-BETAdev09.10.1.exe on Windows XP with a 1.6GHz processor. Evaluating "3 + 4" or "Time now" takes about 1 sec or more to print the result. Is this expected for this beta version? -- View this message in context: http://n2.nabble.com/Performance-in-Workspace-tp3772302p3772302.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

6 9

Re: [Pharo-project] Pharo - Squeak VM bug?
by StÃ©phane Ducasse Oct. 6, 2009

Oct. 6, 2009

On Oct 6, 2009, at 10:03 AM, Petr VÃ¡cha wrote: > Hi there, > sorry for contacting you directly, there are reasons why I do not have > a Google account. Sorry for that. but you do not have too. the mail-ling is free access. > I believe I found cool bug (probably in Squeak VM, also affects > Exupery > VM), but also other Smalltalks are affected, incl. Smalltalk/X, Cuis > and Squeak itself .. not checked with Visual Works though. > > Just try to inspect "a:=Array new: SmallInteger maxVal." and see what > is value of "a" variable - interestingly, primitive (in Squeak VM, > primitive > 71) DOES NOT fail on too big arguments (however, it fails on negative > arguments). What is interesting is that Smalltalk/X crashes, while > Cuis, > Pharo a Squeak actually assign "a" a value - check yourself what is > assigned (depends on Smalltalk variant). No Smalltalk variant I > checked > fails a primitive. > > Maybe it is on purpose, but I believe this situation shall be somehow > signalled to developer as "Array>>new:" method did not provide what > is expected (returns junk). > > In case of a miscall, sorry for your time. > > Greets, > Petr Vacha > > > >

1 0

[Pharo-project] [Free Book] Computer Programming using GNU Smalltalk
by Torsten Bergmann Oct. 6, 2009

Oct. 6, 2009

Hi Stef, a new book to add to your list of free Smalltalk books. http://canol.wordpress.com/2009/10/04/computer-programming-using-gnu-smallt… Bye Torsten -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

1 0

[Pharo-project] How to edit in the wiki
by Gabriel Cotelli Oct. 6, 2009

Oct. 6, 2009

Hi, I want to update: http://code.google.com/p/pharo/wiki/PackagesTestedInPharoto include packages that I have tested that loads Ok on Pharo. Can anybody give me access to change this? Thanks, Gabriel

2 1

Re: [Pharo-project] [BUG]UndefinedObject(Object)>>doesNotUnderstand: #null
by Damien Cassou Oct. 5, 2009

Oct. 5, 2009

Hi, On Mon, Oct 5, 2009 at 7:19 AM, <anlarionov(a)gmail.com> wrote: > Almost all refactorings ends with this DNU. Is it platform specific? Or > maybe i miss something could you please describe all the steps to reproduce that from a clean download? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

2 1

[Pharo-project] Update stuck at #10457
by Adrian Lienhard Oct. 5, 2009

Oct. 5, 2009

Hi, I tried to update from an older image and got stuck in update #10457. I get a warning with the following text: "Please note that adding package references as strings (such as 'Kernel-MikeRoberts.408') is no longer supported, because Gofer cannot guess your naming conventions. Adapt your code to either call #addPackage: (for full package names e.g. Gofer), #addVersion: (for complete version names, e.g. Gofer-lr.54) or #addPrefix: (for incomplete version names, e.g. Gofer-lr). This lets Gofer know what exactly you want, and in return it will more likely do what you expect." I click proceed but the warning appears again. After probably 5x proceeding I get a MNU: BytecodeAgnosticMethod>>doesNotUnderstand: #blockExtentsToTempRefs from which I cannot recover. Is this a known issue? Cheers, Adrian

4 5

[Pharo-project] Fwd: [squeak-dev] The Trunk: Compiler-jcg.85.mcz
by StÃ©phane Ducasse Oct. 5, 2009

Oct. 5, 2009

Begin forwarded message: > From: commits(a)source.squeak.org > Date: September 30, 2009 10:14:22 AM GMT+02:00 > To: squeak-dev(a)lists.squeakfoundation.org > Subject: [squeak-dev] The Trunk: Compiler-jcg.85.mcz > Reply-To: squeak-dev(a)lists.squeakfoundation.org > > Joshua Gargus uploaded a new version of Compiler to project The Trunk: > http://source.squeak.org/trunk/Compiler-jcg.85.mcz > > ==================== Summary ==================== > > Name: Compiler-jcg.85 > Author: jcg > Time: 30 September 2009, 1:14:16 am > UUID: 21a5f88d-4107-48c3-b41c-d5ea735319a7 > Ancestors: Compiler-tfel.84 > > Revert to lazy-initialization of method properties, which is used by > the externally-maintained Prolog package (which loads cleanly into > 3.10.2, but not trunk). > > Part 1 of 2... need to first re-add the #properties method to Parser > before changing methods to send it. > > =============== Diff against Compiler-tfel.84 =============== > > Item was added: > + ----- Method: Parser>>properties (in category 'pragmas') ----- > + properties > + ^ properties ifNil: [ properties := AdditionalMethodState new ]! > >

2 2

[Pharo-project] [update] #10467
by Marcus Denker Oct. 5, 2009

Oct. 5, 2009

10467 ----- Issue 1260: [Regression?] Issue 277 (SelfEvaluating Arrays) wasn't integrated in beta-10462 Issue 987: 'stack top' variable on debugger crashes it Issue 1269: findLastOccurenceOfStringFix has broken a previous WideString patch -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

1 0

Oct. 5, 2009

Begin forwarded message: > From: commits(a)source.squeak.org > Date: October 1, 2009 8:21:58 AM GMT+02:00 > To: squeak-dev(a)lists.squeakfoundation.org > Subject: [squeak-dev] The Trunk: Compiler-jcg.87.mcz > Reply-To: squeak-dev(a)lists.squeakfoundation.org > > Joshua Gargus uploaded a new version of Compiler to project The Trunk: > http://source.squeak.org/trunk/Compiler-jcg.87.mcz > > ==================== Summary ==================== > > Name: Compiler-jcg.87 > Author: jcg > Time: 30 September 2009, 11:21:53 am > UUID: 71bf4e8d-f9f3-4371-a218-ad31a985cfd8 > Ancestors: Compiler-ul.86 > > Revert to lazy-initialization of method properties, which is used by > the externally-maintained Prolog package (which loads cleanly into > 3.10.2, but not trunk). > > Part 2 of 2... need to load -jcg.85 first (this is taken care of by > the Monticello Configuration update-jcg.32.mcm) > > =============== Diff against Compiler-ul.86 =============== > > Item was changed: > ----- Method: Parser>>addPragma: (in category 'pragmas') ----- > addPragma: aPragma > + properties := self properties copyWith: aPragma! > - properties := properties copyWith: aPragma! > > Item was changed: > ----- Method: Parser>>method:context:encoder: (in category > 'expression types') ----- > method: doit context: ctxt encoder: encoderToUse > " pattern [ | temporaries ] block => MethodNode." > > | sap blk prim temps messageComment methodNode | > - properties := AdditionalMethodState new. > encoder := encoderToUse. > sap := self pattern: doit inContext: ctxt. > "sap={selector, arguments, precedence}" > + self properties selector: (sap at: 1). > - 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! > > Item was changed: > ----- Method: > MethodNode > >>selector:arguments:precedence:temporaries:block:encoder:primitive: > (in category 'initialize-release') ----- > selector: selOrFalse arguments: args precedence: p temporaries: > temps block: blk encoder: anEncoder primitive: prim > + > + self > + selector: selOrFalse > + arguments: args > + precedence: p > + temporaries: temps > + block: blk encoder: > + anEncoder > + primitive: prim > + properties: AdditionalMethodState new.! > - "Initialize the receiver with respect to the arguments given." > - > - encoder := anEncoder. > - selectorOrFalse := selOrFalse. > - precedence := p. > - arguments := args. > - temporaries := temps. > - block := blk. > - primitive := prim! > > Item was changed: > ----- Method: Parser>>pragmaPrimitives (in category 'pragmas') ----- > pragmaPrimitives > | primitives | > + self properties isEmpty ifTrue: > - properties isEmpty ifTrue: > [^0]. > primitives := properties pragmas select: > [:pragma| > self class primitivePragmaSelectors includes: pragma keyword]. > primitives isEmpty ifTrue: > [^0]. > primitives size > 1 ifTrue: > [^self notify: 'Ambigous primitives']. > ^self perform: primitives first keyword withArguments: primitives > first arguments! > >

2 1

[Pharo-project] Copy for SequenceableCollection subclasses? (Was: Fix for 987)
by Henrik Johansen Oct. 5, 2009

Oct. 5, 2009

Somewhat related, at least I noticed it when debugging this: Sending copy to a LinkedList or a Semaphore will give back an array, since it uses shallowCopy from SequenceableCollection. Probably applies to more of SequenceableCollection's subclasses too, f.ex. DirectoryEntry for which copy leads to an MNU. Another side-effect of strange class-hierarchy, I guess :) Not quite sure how/if you want to implement those differently. Submitted to tracker as Issue1272. Cheers, Henry On Oct 5, 2009, at 1:12 38PM, StÃ©phane Ducasse wrote: > Thanks we will integrate that as soon as we can breath :) > > On Oct 5, 2009, at 12:14 PM, Henrik Johansen wrote: > >> Updated Issue987 with a SLICE in Inbox, which "fixes" the DNU in the >> way below. >> Used printString instead of asString as proposed by HernÃ¡n, as it (in >> principle) should be more robustly implemented and thus more suited >> for debugger display. >> (If sig's idea from some time back was adopted, this should be >> debugString instead of printString, of course). >> >> Cheers, >> Henry >> >> On Oct 5, 2009, at 11:51 23AM, Henrik Johansen wrote:

3 7