- Pharo-dev - lists.pharo.org

Re: [Pharo-project] deprecated: in Deprecated14

by StÃ©phane Ducasse

+ 1 Given a date and a version is a nice way to educate people to traceability. > Marcus Denker-4 wrote >> >> I think the idea was to deprecate deprecated: so people use the one with >> more >> infos... (deprecated:on:in:) >> >> But for small external projects, deprecated: is just fine and there are >> users. So >> I suggest we just move it out of the deprecated package and have it as a >> simple >> to use version of deprecation tagging. >> > > It was quite a bit of work to clean the system of calls to #deprecated: > http://code.google.com/p/pharo/issues/detail?id=4718 > > If it's an important feature of other projects (I don't see the value over > the more informative version; who has a use case?), maybe the best thing is > for it to be loadable but not included by default? If it's left in the > image, I'm sure habit and inertia will have people continue to use it in the > core image, which is not what we want. > > Sean > > -- > View this message in context: http://forum.world.st/deprecated-in-Deprecated14-tp4107546p4108889.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Nov. 25, 2011

[Pharo-project] Fuel bug: infinite recursion in "analyzer when:substituteBy:"

by Yanni Chiu

The attached test case, reproduced below: | result | self analyzer when: [:x | FLPair = x class and: [x left isNil not] ] substituteBy: [:x | x copy left: $A ]. result := self resultOfSerializeAndMaterialize: (FLPair new left: $a; right: $b; yourself). self assert: result left = $A. causes an infinite loop with IdentityDictionary (see stack trace at end). The similar test case #testTransientPairLeft, works because the guard condition is negated by the replacement (i.e. "x left isNil not" is made false by the replacement). The attached test case does not make "x left isNil not" false. It causes an infinite recursion, so use "ctrl-." to stop it before too long. Is this a bug, or the intention of the #when:substituteBy: feature? I've worked around it, by making sure to always have the substituted value fail the guard clause. -- Yanni ==== stack trace ==== IdentityDictionary>>scanFor: IdentityDictionary(HashedCollection)>>findElementOrNil: IdentityDictionary(Dictionary)>>at:ifAbsent: FLPluggableSubstitutionCluster(FLSubstitutionCluster)>>add:traceWith: FLAnalysis>>mapAndTrace: FLAnalysis>>run [:anObject | (FLAnalysis newWith: self firstInMapperChain root: anObject) run; yourself] in FLAnalyzer>>setDefaultAnalysis FLAnalyzer>>analysisFor: FLSerialization>>analysisStep FLSerialization>>run [:anObject :aStream | (FLSerialization root: anObject on: aStream analyzer: self analyzer) run; yourself] in FLSerializer>>defaultSerialization [self nextPutSignatureOn: aStream. self nextPutVersionOn: aStream. ^ self serializationFactory value: anObject value: aStream] in FLSerializer>>serialize:on: BlockClosure>>ensure: FLSerializer>>serialize:on: [:aStream | self serializer serialize: anObject on: aStream] in FLPluggableSubstitutionTest(FLSerializationTest)>>serialize: [:aStream | aValuable value: aStream binary] in FLFileStreamStrategy>>writeStreamDo: [anotherBlock value: file] in MultiByteFileStream class(FileStream class)>>detectFile:do: BlockClosure>>ensure: MultiByteFileStream class(FileStream class)>>detectFile:do: MultiByteFileStream class(FileStream class)>>forceNewFileNamed:do:

Nov. 25, 2011

Re: [Pharo-project] ProtoObject basicNew :)

by StÃ©phane Ducasse

On Nov 25, 2011, at 10:09 PM, Toon Verwaest wrote: > Ok, I guess I was confused by your initial question: "the methods that I should define in a subclass of ProtoObject so that I can use basicNew"... :) :) Yes it is more the methods that I should define to have a usable class (browse, doit, inspect it). I will probably have to do it by try and error. Stef > > On 11/25/2011 10:05 PM, StÃ©phane Ducasse wrote: >> I'm confused. >> I'm not creating a class but an instance. >> if it would be Behavior basicNew then yes I made sure that we could do Behavior new and not crashing the system back in Squeak. >> >> On Nov 25, 2011, at 9:45 PM, Toon Verwaest wrote: >> >>> With the magic number I mean the number that defines the object's structure. It's one of the first 3 instance variables of every class, encoding how many instance variables there are; what kind of object it is supposed to be (normal, array, bytes, words...). Every "class" basically needs 3 instance variables. 1 defines the structure, 1 the superclass, 1 the behavior (method dictionary). I don't know the other; but just look at some class to know what the order is. >> Yes format, methodDict, superclass (probably in a different order). >> And format is ugly because not explicit and coded in several place like instSpec (berk) >> >>> And yes, if you want to inspect the object, you'll need to support whatever protocol your inspector is using. >>> >>> The format is formed as follows: >>> >>> format >>> | fieldSize sizeHiBits format | >>> fieldSize := self fieldSize + 1. >>> sizeHiBits := fieldSize // 64. >>> format := sizeHiBits. >>> format := (format bitShift: 5) + compactClassIndex. >>> format := (format bitShift: 4) + self instanceSpecification. >>> format := (format bitShift: 6) + (fieldSize \\ 64). >>> format := (format bitShift: 1). >>> ^ format >>> >>> If I read it correctly (just glancing), instance specification specifies if it's arrayed and if it has fields. 0 -> no fields, not arrayed, 1 -> fields, not arrayed, 2 -> arrayed no fields, 3 -> arrayed fields. >>> >>> >>> HTH, >>> Toon >>> >>> On 11/25/2011 09:31 PM, StÃ©phane Ducasse wrote: >>>> Apparently I can do a doit I was naively doing an inspect ;) >>>> >>>> >>>>> Don't you just need the basicNew primitive, and make sure that the "magic number" is set in the object that has the basicNew installed to something that makes sense? >>>>> >>>> I do not know what is the magic number. >>>> I guess that my problem was that I have first to define what is the minimal behavior. >>>> >>>> >>>>> If you want to send messages to the object, probably also best install some dictionary as the method dict instvar. >>>>> >>>> But I guess that ProtoObject has some behavior since I can browse the class with a browser. >>>> >>>> >>>> >>>>> Toon >>>>> >>>>> On 11/25/2011 09:26 PM, StÃ©phane Ducasse wrote: >>>>> >>>>>> Hi >>>>>> I would like to know the methods that I should define in a subclass of ProtoObject so that I can use basicNew. >>>>>> Does any of you have an idea? >>>>>> >>>>>> Stef >>>>>> >> > >

Nov. 25, 2011

Re: [Pharo-project] deprecated: in Deprecated14

by Sean P. DeNigris

Marcus Denker-4 wrote > > I think the idea was to deprecate deprecated: so people use the one with > more > infos... (deprecated:on:in:) > > But for small external projects, deprecated: is just fine and there are > users. So > I suggest we just move it out of the deprecated package and have it as a > simple > to use version of deprecation tagging. > It was quite a bit of work to clean the system of calls to #deprecated: http://code.google.com/p/pharo/issues/detail?id=4718 If it's an important feature of other projects (I don't see the value over the more informative version; who has a use case?), maybe the best thing is for it to be loadable but not included by default? If it's left in the image, I'm sure habit and inertia will have people continue to use it in the core image, which is not what we want. Sean -- View this message in context: http://forum.world.st/deprecated-in-Deprecated14-tp4107546p4108889.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 25, 2011

Re: [Pharo-project] How turn on Halo's?

by Helene Bilbo

Denis Kudriashov wrote > > Can I turn on halos. And is rotating morphs supported in pharo? > I love the rotating Morphs in Squeak! I found the functionality still in Pharo, but only in RectangleMorph. But it seems to work fine to just copy the methods from the t-rotating category of RectangleMorph back into Morph. So Browsers can be rotated again, while you type text into them :) I think itâs a very important feature, even if it is of no professional use. really. Best regards, Helene. -- View this message in context: http://forum.world.st/How-turn-on-Halo-s-tp2227309p4108883.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 25, 2011

Re: [Pharo-project] object format of true, false, nil and others...

by StÃ©phane Ducasse

Thanks for now I should eat my own dog food and do it and stop talking or even thinking about it. But I'm sucked by the world around me (wife, kids, colleagues, mail, admin, I should go to an island without humans and internet). Stef On Nov 25, 2011, at 10:14 PM, Toon Verwaest wrote: > >>> That's what we do in Pinocchio. We just ask for instSize, amongst other things... Maybe I'm missing something? :) >> right now I will start with stub to get some momentum and think after. >> I was reading the bootstrap of Mate and it should be close to the one of pinocchio. >> I'm reading also micro squeak and gst >> But I should bump into the walls to progress. >> >> Stef > Let me know if you have specific questions I can help with... I'm not hyper-responsive (nor reading mailing lists) since working on paper and thesis, but if you mail me directly I might be able to help out with questions at least. > > Toon >

Nov. 25, 2011

Re: [Pharo-project] object format of true, false, nil and others...

by Toon Verwaest

>> That's what we do in Pinocchio. We just ask for instSize, amongst other things... Maybe I'm missing something? :) > right now I will start with stub to get some momentum and think after. > I was reading the bootstrap of Mate and it should be close to the one of pinocchio. > I'm reading also micro squeak and gst > But I should bump into the walls to progress. > > Stef Let me know if you have specific questions I can help with... I'm not hyper-responsive (nor reading mailing lists) since working on paper and thesis, but if you mail me directly I might be able to help out with questions at least. Toon

Nov. 25, 2011

Re: [Pharo-project] object format of true, false, nil and others...

by StÃ©phane Ducasse

On Nov 25, 2011, at 10:03 PM, Toon Verwaest wrote: > To reply to the question from our pov: > > In Pinocchio we actually need that nil, true and false fall within the first 4gb of virtual memory space, since our native code directly addresses those objects; and AMD64 code can only use 32bits for direct addresses. > > This is kinda sucky since OSX thinks it's a good idea to reserve the whole first 4gb virtual address space as "null memory", to ensure they really really really capture all accidental NULL-pointer dereferences. And obviously the standard 4K isn't enough for OSX developers. Oh well, we managed to fix that with some ld flag on OSX. > > We do this since it gives a very slight advantage in performance, and we don't seriously expect nil, true and false to ever change. And if they do... we can still visit all code in the system and change it :) right now I just need a placeholder after I imagine that the specialObjectArray and system tracer can let me specify what I want in the resulting image. And may be I could use mate explicit object format description to migrate (instead of systemTracer). > > cheers, > Toon > > On 11/23/2011 11:25 PM, Stefan Marr wrote: >> Hi: >> >> On 23 Nov 2011, at 22:59, StÃ©phane Ducasse wrote: >>> imagine that I want to bootstrap our nice kernel. >>> I will need to somehow create a new nil, true, false, instances of new classes Undefined, True, False. >>> Such instances will then be put on the SpecialObjectArray somehow. >> Something kind of related: >> >> When debugging the VM, I am happy that I always encounter the same object as the first object in the heap. It is some strange string (think it encodes an error message or so). >> >> However, my thought was, also for other purposes, would it be possible to have these special objects sorted to the beginning? Especially, the nilObj would be very handy to have as the first object. >> >> That would need special VM support to arrange it that way, but knowing the nilObj from the very beginning would allow my to initialize some of my hacks more consistently, avoiding C-level NULLs and runtime checks. >> >> Just an idea, vaguely related to the question. >> >> Would be interesting to hear whether there are any historical insights with regard to ordering objects in the image. >> Guess it is not done because nobody needed it. (and then there isn't really a primitive for it, and a moving GC might also be contra-productive, etc.) >> >> Best regards >> Stefan >> >> >> >>> Stef > >

Nov. 25, 2011

Re: [Pharo-project] ProtoObject basicNew :)

by Toon Verwaest

Ok, I guess I was confused by your initial question: "the methods that I should define in a subclass of ProtoObject so that I can use basicNew"... :) On 11/25/2011 10:05 PM, StÃ©phane Ducasse wrote: > I'm confused. > I'm not creating a class but an instance. > if it would be Behavior basicNew then yes I made sure that we could do Behavior new and not crashing the system back in Squeak. > > On Nov 25, 2011, at 9:45 PM, Toon Verwaest wrote: > >> With the magic number I mean the number that defines the object's structure. It's one of the first 3 instance variables of every class, encoding how many instance variables there are; what kind of object it is supposed to be (normal, array, bytes, words...). Every "class" basically needs 3 instance variables. 1 defines the structure, 1 the superclass, 1 the behavior (method dictionary). I don't know the other; but just look at some class to know what the order is. > Yes format, methodDict, superclass (probably in a different order). > And format is ugly because not explicit and coded in several place like instSpec (berk) > >> And yes, if you want to inspect the object, you'll need to support whatever protocol your inspector is using. >> >> The format is formed as follows: >> >> format >> | fieldSize sizeHiBits format | >> fieldSize := self fieldSize + 1. >> sizeHiBits := fieldSize // 64. >> format := sizeHiBits. >> format := (format bitShift: 5) + compactClassIndex. >> format := (format bitShift: 4) + self instanceSpecification. >> format := (format bitShift: 6) + (fieldSize \\ 64). >> format := (format bitShift: 1). >> ^ format >> >> If I read it correctly (just glancing), instance specification specifies if it's arrayed and if it has fields. 0 -> no fields, not arrayed, 1 -> fields, not arrayed, 2 -> arrayed no fields, 3 -> arrayed fields. >> >> >> HTH, >> Toon >> >> On 11/25/2011 09:31 PM, StÃ©phane Ducasse wrote: >>> Apparently I can do a doit I was naively doing an inspect ;) >>> >>> >>>> Don't you just need the basicNew primitive, and make sure that the "magic number" is set in the object that has the basicNew installed to something that makes sense? >>>> >>> I do not know what is the magic number. >>> I guess that my problem was that I have first to define what is the minimal behavior. >>> >>> >>>> If you want to send messages to the object, probably also best install some dictionary as the method dict instvar. >>>> >>> But I guess that ProtoObject has some behavior since I can browse the class with a browser. >>> >>> >>> >>>> Toon >>>> >>>> On 11/25/2011 09:26 PM, StÃ©phane Ducasse wrote: >>>> >>>>> Hi >>>>> I would like to know the methods that I should define in a subclass of ProtoObject so that I can use basicNew. >>>>> Does any of you have an idea? >>>>> >>>>> Stef >>>>> >

Nov. 25, 2011

Re: [Pharo-project] object format of true, false, nil and others...

by StÃ©phane Ducasse

>>> >>> >> but you should be able to calculate size taken from object format >> descriptor, don't you? > That's what we do in Pinocchio. We just ask for instSize, amongst other things... Maybe I'm missing something? :) right now I will start with stub to get some momentum and think after. I was reading the bootstrap of Mate and it should be close to the one of pinocchio. I'm reading also micro squeak and gst But I should bump into the walls to progress. Stef

Nov. 25, 2011