- Pharo-dev - lists.pharo.org

[Pharo-project] How detect a primitve?
by James Ladd Aug. 3, 2010

Aug. 3, 2010

Hi All, Im working on the bytecodes for methods and I am wondering, how can I tell if a compiled methods bytecode contains (starts) with a primitive, and which primitive it is? Rgs, James.

2 1

Re: [Pharo-project] update to OCompletion
by Romain Robbes Aug. 3, 2010

Aug. 3, 2010

> > > Message: 6 > Date: Tue, 3 Aug 2010 00:46:07 +0200 (CEST) > From: Levente Uzonyi <leves(a)elte.hu> > Subject: Re: [Pharo-project] update to OCompletion > To: "Pharo Development (Pharo-project(a)lists.gforge.inria.fr > Development <pharo-project(a)lists.gforge.inria.fr>)" > <Pharo-project(a)lists.gforge.inria.fr> > Message-ID: <Pine.LNX.4.64.1008030045560.16259(a)login03.caesar.elte.hu> > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > On Mon, 2 Aug 2010, Romain Robbes wrote: > >> Hi All, >> >> I just committed: >> http://squeaksource.com/OCompletion/Ocompletion-RomainRobbes.64.mcz >> >> the changes are: >> >> -incorporated Lukas' smart characters algorithm (thanks Lukas!) >> -removed enter to insert a completion; only tab works now. >> -delayed the switch to eCompletion's completion algorithm, hence the slowdown when using the down arrow happens only after the third time pressing it (after OCompletion's all of OCompletion's menu items). > > Cool. Does it work in Squeak? > Early versions did, but I'm not sure this one does. When I first released it, the Squeak community showed little interest, so I focused on Pharo. Romain > > Levente -- Romain Robbes http://romain.robb.es rrobbes(a)dcc.uchile.cl

2 1

[Pharo-project] [update 1.2] #12079
by StÃ©phane Ducasse Aug. 3, 2010

Aug. 3, 2010

12079 ----- - Issue 2655: Fix the other dependencies of asContextWithSender:

1 0

[Pharo-project] About MethodContextTest
by StÃ©phane Ducasse Aug. 3, 2010

Aug. 3, 2010

in Squeak there are a couple of MethodContextTest. do you remember why we removed them? Stef

1 0

[Pharo-project] about value:
by StÃ©phane Ducasse Aug. 3, 2010

Aug. 3, 2010

Henrik I integrated your value, value: cleans and I get such kind of error now. stackp = 2 and not zero. I'm puzzled. because I thought that the other code was not executed since it was covered by a primitive that would do the right job. pushArgs: args "<Array>" from: sendr "<ContextPart>" "Helps simulate action of the value primitive for closures. This is used by ContextPart>>runSimulated:contextAtEachStep:" stackp ~= 0 ifTrue: [self error: 'stack pointer should be zero!']. closureOrNil ifNil: [self error: 'context needs a closure!']. args do: [:arg| self push: arg]. 1 to: closureOrNil numCopiedValues do: [:i| self push: (closureOrNil copiedValueAt: i)]. sender := sendr

1 2

[Pharo-project] [update 1.2] #12078
by StÃ©phane Ducasse Aug. 3, 2010

Aug. 3, 2010

12078 ----- - Issue 2661: File name correction for unix to allow. Thanks Eliot Miranda, German Ardino. - Issue 2122: superclassOrder: is defined on Changeset. Now defined on Class. Thanks Steven Freeman. - Fixed OSPlatform vmVersion

1 0

[Pharo-project] [update 1.2] #12077
by StÃ©phane Ducasse Aug. 3, 2010

Aug. 3, 2010

12077 ----- - Issue 2347: fixing Problem with previous release vmVersion was missing. - Issue 2745: Text>>fromString; , does not add by default a (TextColor color: Color black ) attribute. Thanks Fernando Olivero. - Issue 2662: value: primitives. Thanks Eliot Miranda, Henrik Johanssen. - Issue 2603: isRunningCog. Thanks Andreas Raab, German Arduino. - Issue 2609: getSystemAttribute: 2 -> documentPath. Thanks German Arduino.

2 2

[Pharo-project] Text>>fromString: and String>>asText
by Fernando olivero Aug. 3, 2010

Aug. 3, 2010

Name: SLICE-Issue-2745-TextFromStringAddingBlackAttribute-FernandoOlivero.1 Author: FernandoOlivero Time: 3 August 2010, 3:32:02 pm UUID: 85d642dd-87c1-4cab-9aa2-629ab10a6bd8 Ancestors: Dependencies: Collections-Text-FernandoOlivero.37 Added the black color attribute to all text's, created sending #asText ( which in turn sends Text>>fromString: ). Which produces a transparent color when rendered sending: aCanvas paragraph: paragraph bounds: bounds color: self fillStyle I've added the black color attribute by default.

1 0

Aug. 3, 2010

12075 ----- - Issue 2296: Point>>closeTo. Thanks Alexandre Bergel and Henrik Johanssen. - SUnit Announcement post fix. - Issue 2617: Fix restart in blocks in debugger. Thanks Henrik Johanssen. - Issue 2364: FileList menu more... is bogus. Thanks Carlo Teixeira - Issue 1767: Method Finder gives UndefinedObject error on search. Thanks Alexandre Bergel. Thanks Marcus, patchinko and Gary. Stef

1 0

[Pharo-project] Something I don't see in ImageSegment
by Mariano Martinez Peck Aug. 3, 2010

Aug. 3, 2010

Hi. ImageSegment uses GC to compute the out pointers. Basically, to a given array of roots (a graph) it does: 1) It marks the rootArray and all root objects by turning on the Garbage Collector bit in the object header of those particular objects. 2) Then does a mark pass over all objects. This will stop at our marked roots leaving our segment unmarked in their shadow. 3) Finally, it unmarks the rootArray and all root objects. 4) Only external objects are now marked. The unmarked objects in the graph of objects of the arrays are those who will be put in the WordArray (the segment) and those who are marked to the outPointers. However, I don't see where step 2) is done in Interpreter >> primitiveStoreImageSegment In a piece of such method it does: "Then do a mark pass over all objects. This will stop at our marked roots, thus leaving our segment unmarked in their shadow." savedYoungStart := youngStart. youngStart := self startOfMemory. "process all of memory" "clear the recycled context lists" freeContexts := NilContext. freeLargeContexts := NilContext. self markAndTraceInterpreterOops. "and special objects array" youngStart := savedYoungStart. "Finally unmark the rootArray and all root objects." self longAt: arrayOfRoots put: ((self longAt: arrayOfRoots) bitAnd: AllButMarkBit). ......continue....... But here I see it is only marking Interpreter oops, not all objects. And I don't see where all objects are marked even in the code that follows this little piece. You can see the comment: "Then do a mark pass over all objects" and even without the comment it makes sense to mark all objects in order to detect outPointers. Does anyone has a hint? Thanks Mariano

3 7