May 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] A comparative article (was Re: [squeak-dev] [ANN] STON - Smalltalk Object Notation)

by Douglas Brebner

On 09/05/2012 09:08, GÃ¶ran Krampe wrote: > Ok, regarding changing the syntax of Smalltalk: > > - Personally I don't care that much for ANSI. It's dead. I think > Smalltalk needs to evolve and bloody hell, you have *Traits* in Pharo, > that is a HUGE difference compared to a bit of literal changes. ;) > > - If we *do* decide to "Hey, let's take a look at our literal syntax", > then we should probably see if we can harmonize a bit. Again, see my > article for some thoughts in that area. > > I agree that Smalltalk literals are quite powerful but I think they > can be improved. One thing that occurred to me after reading your article was with a formal prefix for #literal and Â§dynamic syntax, wouldn't it open the door to cleanly supporting other, even non-textual objects directly in the source? Whether that's a good idea or not is another question :)

May 9, 2012

Re: [Pharo-project] Strangest object ever seen?

by Marcus Denker

On May 8, 2012, at 11:49 PM, Pavel Krivanek wrote: > Hi, > > If you take the latest Pharo 2.0 image from Jenkins (20059) and you execute the expression: > > (Metaclass allInstances select: [:c | c superclass = ProtoObject class]) inspect > It seems to disappear when evaluating Smalltalk cleanUp. Maybe we should do that anyway on the build server for each build... -- Marcus Denker -- http://marcusdenker.de

May 9, 2012

Re: [Pharo-project] A comparative article (was Re: [squeak-dev] [ANN] STON - Smalltalk Object Notation)

by Esteban A. Maringolo

GÃ¶ran Krampe wrote > > I don't want to sound like a broken record - but you do realize that I > wrote about this in the article and mentioned this exact syntax? > > I know, the article was a tad long - but just go to planet.smalltalk.org > and search down to "Sidestory: Adding literal Dictionaries to Smalltalk?". > > regards, GÃ¶ran > I do realize, and read the entire post. I simply didn't want to just say "+1" to everything you state in the blog post, and did a summary of what's interesting for me. :) Regards! -- View this message in context: http://forum.world.st/ANN-STON-Smalltalk-Object-Notation-tp4609808p4620638.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 9, 2012

Re: [Pharo-project] MC, Ring and RPackage dependencies

by StÃ©phane Ducasse

> Hi, > > I yesterday put Pharo Kernel Gofer 2.0 job into operation (together > with some other dependent like Seaside and OSProcess evaluator). But > unfortunatelly I have to say it was quite complicated and I had to do > some ugly hacks because we do not have solved dependencies between > Monticello, Ring and RPackage. > > The loading order we use now is: > 'Monticello' > 'MonticelloConfigurations' > 'Ring-Core-Kernel' > 'RPackage-Core' > 'RPackage-SystemIntegration' Pavel this is strange because RPackage was always managed using Metacello. Now we should fix the dependencies. > Authors of this packages should know that this are primitive packages > that cannot be loaded in one bundle via Monticello but must be loaded > one by one as standard *.st files. That means that that we have to > have well known and working loading order. As an example, currently > the initialization of the package 'RPackage-Core' is dependent on > presence of 'RPackage-SystemIntegration'. > > Cheers, > -- Pavel >

May 9, 2012

Re: [Pharo-project] Strangest object ever seen?

by StÃ©phane Ducasse

On May 9, 2012, at 2:14 PM, Pavel Krivanek wrote: > Some next interesting information: > > o := ((Metaclass allInstances detect: [:c | c superclass = ProtoObject > class]) instVarNamed: #thisClass). 1. > > Smalltalk allClassesAndTraits select: [:c | o isKindOf: c] -> an > OrderedCollection(Behavior Class ClassDescription Object ProtoObject) > > Smalltalk allClasses select: [:c | o class == c] -> an > OrderedCollection() "WTF" > > o subclasses -> #Object "WTF!" > o subclasses class -> ByteSymbol "WTF!! should be Array" > o superclass -> ProtoObject "WTF" > (o methodDict keys asSortedCollection first: 50) = (Object methodDict > keys asSortedCollection first: 50) -> true "wasn't it Object in better > times?" Is WTF? Really strange. Pavel you can tell the updater to update until a certain number.

May 9, 2012

Re: [Pharo-project] A comparative article (was Re: [squeak-dev] [ANN] STON - Smalltalk Object Notation)

by GÃ¶ran Krampe

On 05/09/2012 03:55 PM, Esteban A. Maringolo wrote: > I would like to share my quick two cents regarding this subject. > > 1st cent. I would stick with JSON. Even though I find STON slick, I would > not deviate from something that is mainstream and all Smalltalk dialects > already support. > > 2nd cent. A Dictionary literal syntax would be useful too. I would like to > have it. > > It could be something like #{'this' -> 1. 'that' -> 2 }, and keep {1. 2} for > dynamic arrays. I don't want to sound like a broken record - but you do realize that I wrote about this in the article and mentioned this exact syntax? I know, the article was a tad long - but just go to planet.smalltalk.org and search down to "Sidestory: Adding literal Dictionaries to Smalltalk?". regards, GÃ¶ran

May 9, 2012

Re: [Pharo-project] A comparative article (was Re: [squeak-dev] [ANN] STON - Smalltalk Object Notation)

by Esteban A. Maringolo

I would like to share my quick two cents regarding this subject. 1st cent. I would stick with JSON. Even though I find STON slick, I would not deviate from something that is mainstream and all Smalltalk dialects already support. 2nd cent. A Dictionary literal syntax would be useful too. I would like to have it. It could be something like #{'this' -> 1. 'that' -> 2 }, and keep {1. 2} for dynamic arrays. Regards, -- Esteban. -- View this message in context: http://forum.world.st/ANN-STON-Smalltalk-Object-Notation-tp4609808p4620499.… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 9, 2012

Re: [Pharo-project] Strangest object ever seen?

by Guillermo Polito

On Wed, May 9, 2012 at 3:39 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > >> Now I do not understand why this guy cannot get printed. > >> > >> I do not see why > >> > >> ClassDescription>>printOn: aStream > >> aStream nextPutAll: self name > >> > >> Metaclass>>name > >> "Answer a String that is the name of the receiver, either > 'Metaclass' or > >> the name of the receiver's class followed by ' class'." > >> > >> thisClass == nil > >> ifTrue: [^'a Metaclass'] > >> ifFalse: [^thisClass name , ' class'] > >> > >> self first soleInstance printString > >> -> leads to have emergency debugger. > > you do not get emergency! > I do not like when we do not get the same bugsâ¦ > > > > self name shows: > > > > a Dictionary(#DependentsFields->a WeakIdentityKeyDictionary(a > > CategoryWidget->a DependentsArray(a PluggableIconListMorph(217841664)) > > a ContextVariablesInspector->a DependentsArray(a > > PluggableListMorph(445382656) a PluggableTextMorph(1046216704)) a > > ContextVariablesInspector->a DependentsArray(a > > PluggableListMorph(290193408) ... ) > > > > The source of printing problems will be in thisClass. > > > > The next interesting thing is that it has no pointers and it is > > removed after garbageCollect. > > So this is a good news :). > > now that I was kind of liking dzindzik... > > > > > -- Pavel > > > > > > > > > >> Stef > >> > >> > >> > >> > >> > > > > >

May 9, 2012

Re: [Pharo-project] Strangest object ever seen?

by StÃ©phane Ducasse

>> Now I do not understand why this guy cannot get printed. >> >> I do not see why >> >> ClassDescription>>printOn: aStream >> aStream nextPutAll: self name >> >> Metaclass>>name >> "Answer a String that is the name of the receiver, either 'Metaclass' or >> the name of the receiver's class followed by ' class'." >> >> thisClass == nil >> ifTrue: [^'a Metaclass'] >> ifFalse: [^thisClass name , ' class'] >> >> self first soleInstance printString >> -> leads to have emergency debugger. you do not get emergency! I do not like when we do not get the same bugsâ¦ > self name shows: > > a Dictionary(#DependentsFields->a WeakIdentityKeyDictionary(a > CategoryWidget->a DependentsArray(a PluggableIconListMorph(217841664)) > a ContextVariablesInspector->a DependentsArray(a > PluggableListMorph(445382656) a PluggableTextMorph(1046216704)) a > ContextVariablesInspector->a DependentsArray(a > PluggableListMorph(290193408) ... ) > > The source of printing problems will be in thisClass. > > The next interesting thing is that it has no pointers and it is > removed after garbageCollect. So this is a good news :). > > -- Pavel > > > > >> Stef >> >> >> >> >> >

May 9, 2012

Re: [Pharo-project] Strangest object ever seen?

by Herby VojÄÃk

The cause of the problem is probably in this: if you try to inspect dzindzik, VM prints out something like "Directory does not have index: 7". If you try dzindzik instVarAt:1, dzindzik instVarAt:2, ... in a row, you get 6, but there is not 7. So dzindzik's class thinks it has (at least) seven inst vars, but in fact in does only have six. Herby

May 9, 2012