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

Re: [Pharo-project] Pharo1.4a#14407 one-click tests failing

by Marcus Denker

On Mar 31, 2012, at 6:56 AM, Martin Sandiford wrote: > There was a bug in timestamp handling for .changes that looks like it > was integrated in #14410. > http://code.google.com/p/pharo/issues/detail?id=5461 > > Without digging further, it looks like this might be the issue with > the two items below. I'd try a newer image. > Yes, this has been fixed and what is shows is that the one-click build is not using the latest image.... I guess because it's build is not triggered automatically. Will be fixed. Marcus -- Marcus Denker -- http://marcusdenker.de

March 31, 2012

[Pharo-project] Zodiac on Linux

by Sean P. DeNigris

When deploying an image to Ubuntu and starting with the Cog VM from Jenkins, I got an error "undefined symbol sqSetIntPropertySSL" from libSqueakSSL.so. Any ideas? Thanks. Sean -- View this message in context: http://forum.world.st/Zodiac-on-Linux-tp4521194p4521194.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 31, 2012

Re: [Pharo-project] Pharo1.4a#14407 one-click tests failing

by Martin Sandiford

There was a bug in timestamp handling for .changes that looks like it was integrated in #14410. http://code.google.com/p/pharo/issues/detail?id=5461 Without digging further, it looks like this might be the issue with the two items below. I'd try a newer image. Martin On Sat, Mar 31, 2012 at 1:13 PM, Bernardo Ezequiel Contreras <vonbecmann(a)gmail.com> wrote: [...] > *** MCStWriterTest>>#testClassMethodDefinition > ' > !MCMockClassA class methodsFor: ''as yet unclassified'' stamp: ''''! > one > > ^ 1! ! > ' size = 79 > > ' > !MCMockClassA class methodsFor: ''as yet unclassified'' stamp: ''ab 7/7/2003 > 23:21''! > one > > ^ 1! ! > ' size = 96 > > so they have different size. > > *** MCStWriterTest>>#testMethodDefinition > ' > !MCMockClassA methodsFor: ''numeric'' stamp: ''''! > one > ^ 1! ! > ' size = 60 > > ' > !MCMockClassA methodsFor: ''numeric'' stamp: ''cwp 8/2/2003 17:26''! > one > ^ 1! ! > ' size = 78 > > it's the same case as before [...]

March 31, 2012

[Pharo-project] Pharo1.4a#14407 one-click tests failing

by Bernardo Ezequiel Contreras

Hi all, I've downloaded the pharo one-click and some tests are failing. Pharo image: *Pharo1.4a#14407* Virtual machine used: CoInterpreter VMMaker-oscog-EstebanLorenzano.139 uuid: 5aa53979-d7d8-4ca3-91fe-cfc3b4109c33 Mar 22 2012, StackToRegisterMappingCogit VMMaker-oscog-EstebanLorenzano.139 uuid: 5aa53979-d7d8-4ca3-91fe-cfc3b4109c33 Mar 22 2012, https://git.gitorious.org/cogvm/blessed.git Commit: e2cad7fb37808cf449802e3e1f80979f0422165b Date: Wed Mar 21 18:02:28 2012 +0100 By: Camillo Bruni <camillobruni(a)gmail.com> Platform Name: unix Class browser used (if applicable): Browser 8330 run, 8313 passes, 10 expected failures, 6 failures, 0 errors, 2 unexpected passes Failures: **** DateAndTimeTest>>#testPrintStringNoOffset* at this line self assert: ('2002-05-16T17:20' asDateAndTime printString = ('2002-05-16T17:20:00+{1}:{2}' format: {localOffsetHours. localOffsetMinutes})). '2002-05-16T17:20' asDateAndTime printString evaluates to '2002-05-16T17:20:00-03:00' and ('2002-05-16T17:20:00+{1}:{2}' format: {localOffsetHours. localOffsetMinutes}) evaluates to '2002-05-16T17:20:00+-3:00' so '2002-05-16T17:20:00-03:00' is not equal to '2002-05-16T17:20:00+-3:00' **** FileDirectoryTest>>#testRecursiveMatching* at this line self assert: (dir matchingEntries: '*.txt') isEmpty. because dir = UnixFileDirectory on '/home/vonbecmann/tmp/pharo-1.4.app/Contents/Resources' has a readme.txt file **** MCClassDefinitionTest>>#testNotValidClassTraitComposition* i cannot debug this failure. it needs more research **** MCClassDefinitionTest>>#testNotValidTraitComposition* i cannot debug this failure. it needs more research **** MCStWriterTest>>#testClassMethodDefinition* ' !MCMockClassA class methodsFor: ''as yet unclassified'' stamp: ''''! one ^ 1! ! ' size = 79 ' !MCMockClassA class methodsFor: ''as yet unclassified'' stamp: ''ab 7/7/2003 23:21''! one ^ 1! ! ' size = 96 so they have different size. **** MCStWriterTest>>#testMethodDefinition* ' !MCMockClassA methodsFor: ''numeric'' stamp: ''''! one ^ 1! ! ' size = 60 ' !MCMockClassA methodsFor: ''numeric'' stamp: ''cwp 8/2/2003 17:26''! one ^ 1! ! ' size = 78 it's the same case as before **** MirrorPrimitiveTests>>#testMirrorSize* i cannot debug this failure. it needs more research any ideas? is this an old build? thanks.

March 31, 2012

Re: [Pharo-project] type-inference: it works!

by Francisco Garau

Another interesting read, is from Peter Ahe who applied the same sort of analysis to the Resilient Smalltalk. http://tinyurl.com/cz9kslu I have some slides explaining my work. I can email them to you, if you wish. Cheers, Francisco On 30 March 2012 22:19, Frank Shearar <frank.shearar(a)gmail.com> wrote: > In case anyone's interested in the paper behind Francisco's work > (thanks Francisco!), you can find "Concrete Type Inference: Delivering > Object Oriented Applications" here: > https://labs.oracle.com/technical-reports/1996/smli_tr-96-52.pdf > > Interestingly, typing 'Display boundBox' fails in Squeak trunk because > "UndefinedObject won't understand #origin:corner:". Odd, since > evaluating same will happily return a Rectangle. I'll look into it and > see what I can find. > > frank > > On 30 March 2012 14:33, Francisco Garau <francisco.garau(a)gmail.com> wrote: > > No unit tests, sorry... > > > > Is not profiling, it's abstract intrepretation using types instead of > > objects. > > > > - Francisco > > > > > > On 30 Mar 2012, at 15:15, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > > > Hi Francisco, > > > > I've tried your implementation. It seems to work in Pharo 1.4. Do you > have > > unit test somewhere? > > How does your profiler work? From what you have said in your email, it > seems > > you are profiling the execution. Is that true? > > > > Cheers, > > Alexandre > > > > > > On 29 Mar 2012, at 18:47, Francisco Garau wrote: > > > > Load the attached ChangeSets: first Ti-Engine and then Ti-Support. > > > > You could then evaluate the below expressions -- watch the Transcript to > see > > which methods are being analysed. > > > > TiSystem current reset. > > string := '3 + 4'. > > Compiler new analyze: string in: nil to: nil notifying: nil ifFail: [1]. > > "=> return {<SmallInteger>} " > > > > TiSystem current reset. > > string := 'Display boundingBox'. > > Compiler new analyze: string in: nil to: nil notifying: nil ifFail: [1]. > > "=> return {<Rectangle origin: <Point x: <SmallInteger> y: > <SmallInteger>> > > corner: <Point x: <SmallInteger> y: <SmallInteger>>>}" > > > > TiSystem current explore. > > > > > > Analysing 'Display boundingBox' shows a couple of surprises: > > > > The code never goes through the #new method (it creates objects using > > #basicNew and #@) > > Object code goes through Object>>value but knowing that the > implementation > > just answers self, it could be easily optimised. > > > > > > I will try to package it more nicely under Monticello -- there are still > a > > few rough edges that need to be polished before getting it to the same > state > > it was in 2001... > > > > Cheers, > > Francisco > > <Ti-Engine.2.cs><Ti-Support.2.cs> > > > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > >

March 30, 2012

Re: [Pharo-project] Emergency evaluator pops up on red tests

by Fabrizio Perin

Hi, Thanks a lot for your effort. It is really strange that just the PHP parser doesn't work. In fact all the parsers I implemented use the same mechanism to ignore instance variables names not related to parsers (so the ignoredNames). Tomorrow morning I will try again to play with the bug. Please let me know if I can do something to help. Thanks a lot again. Cheers, Fabrizio 2012/3/30 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > PPPHPCoreGrammar ignoredNames > #('properties' 'parser' 'keywords') > > > browseSelectorsOn: aBrowser > aBrowser list > title: 'Productions'; > format: [ :class | class asString ]; > display: [ :class | > ((((class allInstVarNames > copyWithoutAll: class ignoredNames) > copyWithoutAll: self rootClass > allInstVarNames) > collect: [ :each | each asSymbol ]) > select: [ :each | class includesSelector: > each ]) > asSortedCollection ]; > selectionAct: [ > StandardToolSet > ^^^^^^^^ > does not exist anymore in 1.4 I guess but > this is should not be related to this bug. > > -> use > Smalltalk tools browser > > browse: self selectedClass > selector: self selectedSelector ] > on: $b entitled: 'browse (b)'; > selectionAct: [ > | class selector | > class := self selectedClass. > selector := self selectedSelector. > (class instVarNames includes: selector) > ifTrue: [ class removeInstVarName: selector > ]. > class removeSelector: selector. > aBrowser entity: self rootModel. > self selectedClass: class ] > on: $r entitled: 'remove (x)' >

March 30, 2012

Re: [Pharo-project] type-inference: it works!

by Frank Shearar

In case anyone's interested in the paper behind Francisco's work (thanks Francisco!), you can find "Concrete Type Inference: Delivering Object Oriented Applications" here: https://labs.oracle.com/technical-reports/1996/smli_tr-96-52.pdf Interestingly, typing 'Display boundBox' fails in Squeak trunk because UndefinedObject won't understand #origin:corner:. Odd, since evaluating same will happily return a Rectangle. I'll look into it and see what I can find. frank On 30 March 2012 14:33, Francisco Garau <francisco.garau(a)gmail.com> wrote: > No unit tests, sorry... > > Is not profiling, it's abstract intrepretation using types instead of > objects. > > - Francisco > > > On 30 Mar 2012, at 15:15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Hi Francisco, > > I've tried your implementation. It seems to work in Pharo 1.4. Do you have > unit test somewhere? > How does your profiler work? From what you have said in your email, it seems > you are profiling the execution. Is that true? > > Cheers, > Alexandre > > > On 29 Mar 2012, at 18:47, Francisco Garau wrote: > > Load the attached ChangeSets: first Ti-Engine and then Ti-Support. > > You could then evaluate the below expressions -- watch the Transcript to see > which methods are being analysed. > > TiSystem current reset. > string := '3 + 4'. > Compiler new analyze: string in: nil to: nil notifying: nil ifFail: [1]. > "=> return {<SmallInteger>} " > > TiSystem current reset. > string := 'Display boundingBox'. > Compiler new analyze: string in: nil to: nil notifying: nil ifFail: [1]. > "=> return {<Rectangle origin: <Point x: <SmallInteger> y: <SmallInteger>> > corner: <Point x: <SmallInteger> y: <SmallInteger>>>}" > > TiSystem current explore. > > > Analysing 'Display boundingBox' shows a couple of surprises: > > The code never goes through the #new method (it creates objects using > #basicNew and #@) > Object code goes through Object>>value but knowing that the implementation > just answers self, it could be easily optimised. > > > I will try to package it more nicely under Monticello -- there are still a > few rough edges that need to be polished before getting it to the same state > it was in 2001... > > Cheers, > Francisco > <Ti-Engine.2.cs><Ti-Support.2.cs> > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre BergelÂ Â http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

March 30, 2012

Re: [Pharo-project] type-inference: it works!

by Frank Shearar

In case anyone's interested in the paper behind Francisco's work (thanks Francisco!), you can find "Concrete Type Inference: Delivering Object Oriented Applications" here: https://labs.oracle.com/technical-reports/1996/smli_tr-96-52.pdf Interestingly, typing 'Display boundBox' fails in Squeak trunk because "UndefinedObject won't understand #origin:corner:". Odd, since evaluating same will happily return a Rectangle. I'll look into it and see what I can find. frank On 30 March 2012 14:33, Francisco Garau <francisco.garau(a)gmail.com> wrote: > No unit tests, sorry... > > Is not profiling, it's abstract intrepretation using types instead of > objects. > > - Francisco > > > On 30 Mar 2012, at 15:15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Hi Francisco, > > I've tried your implementation. It seems to work in Pharo 1.4. Do you have > unit test somewhere? > How does your profiler work? From what you have said in your email, it seems > you are profiling the execution. Is that true? > > Cheers, > Alexandre > > > On 29 Mar 2012, at 18:47, Francisco Garau wrote: > > Load the attached ChangeSets: first Ti-Engine and then Ti-Support. > > You could then evaluate the below expressions -- watch the Transcript to see > which methods are being analysed. > > TiSystem current reset. > string := '3 + 4'. > Compiler new analyze: string in: nil to: nil notifying: nil ifFail: [1]. > "=> return {<SmallInteger>} " > > TiSystem current reset. > string := 'Display boundingBox'. > Compiler new analyze: string in: nil to: nil notifying: nil ifFail: [1]. > "=> return {<Rectangle origin: <Point x: <SmallInteger> y: <SmallInteger>> > corner: <Point x: <SmallInteger> y: <SmallInteger>>>}" > > TiSystem current explore. > > > Analysing 'Display boundingBox' shows a couple of surprises: > > The code never goes through the #new method (it creates objects using > #basicNew and #@) > Object code goes through Object>>value but knowing that the implementation > just answers self, it could be easily optimised. > > > I will try to package it more nicely under Monticello -- there are still a > few rough edges that need to be polished before getting it to the same state > it was in 2001... > > Cheers, > Francisco > <Ti-Engine.2.cs><Ti-Support.2.cs> > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre BergelÂ Â http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > >

March 30, 2012

Re: [Pharo-project] type-inference: it works!

by Alexandre Bergel

Ah okay. But still, I think a comparison is scientifically relevant. Alexandre On 30 Mar 2012, at 14:20, Francisco Garau wrote: > I think they are not comparable. > > They both try to do Type-Inference. But... what is a Type? > > Roel Typer works backwards. > My TiEngine works forwards. > > Roel Typer works backwards because it starts analysing a method a finds a message send, lets say "anObject setup". It then asks the question, who implements the method #setup and if it finds 13 different classes, then those are the "Type" of the anObject. > > My TiEngine starts executing code without actually executing anything. It simulates execution making sure it goes through all the possible execution paths. That's is not always possible, so some compromise should be made. > > Reflection is the killer of any sort of static analysis. > > - Francisco > > > On 30 March 2012 17:17, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Ah okays. Have you made some comparison with the result of Roel Typer? > That would be an interesting point to compare with. > > cheers, > Alexandre > > > > On 30 Mar 2012, at 09:33, Francisco Garau wrote: > >> No unit tests, sorry... >> >> Is not profiling, it's abstract intrepretation using types instead of objects. >> >> - Francisco >> >> >> On 30 Mar 2012, at 15:15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> >>> Hi Francisco, >>> >>> I've tried your implementation. It seems to work in Pharo 1.4. Do you have unit test somewhere? >>> How does your profiler work? From what you have said in your email, it seems you are profiling the execution. Is that true? >>> >>> Cheers, >>> Alexandre >>> >>> >>> On 29 Mar 2012, at 18:47, Francisco Garau wrote: >>> >>>> Load the attached ChangeSets: first Ti-Engine and then Ti-Support. >>>> >>>> You could then evaluate the below expressions -- watch the Transcript to see which methods are being analysed. >>>> >>>> TiSystem current reset. >>>> string := '3 + 4'. >>>> Compiler new analyze: string in: nil to: nil notifying: nil ifFail: [1]. >>>> "=> return {<SmallInteger>} " >>>> >>>> TiSystem current reset. >>>> string := 'Display boundingBox'. >>>> Compiler new analyze: string in: nil to: nil notifying: nil ifFail: [1]. >>>> "=> return {<Rectangle origin: <Point x: <SmallInteger> y: <SmallInteger>> corner: <Point x: <SmallInteger> y: <SmallInteger>>>}" >>>> >>>> TiSystem current explore. >>>> >>>> Analysing 'Display boundingBox' shows a couple of surprises: >>>> The code never goes through the #new method (it creates objects using #basicNew and #@) >>>> Object code goes through Object>>value but knowing that the implementation just answers self, it could be easily optimised. >>>> >>>> I will try to package it more nicely under Monticello -- there are still a few rough edges that need to be polished before getting it to the same state it was in 2001... >>>> >>>> Cheers, >>>> Francisco >>>> <Ti-Engine.2.cs><Ti-Support.2.cs> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 30, 2012

Re: [Pharo-project] direct object manipulation

by Eliot Miranda

On Fri, Mar 30, 2012 at 1:20 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > On Mar 30, 2012, at 9:50 PM, phil(a)highoctane.be wrote: > > > This is a chicken and egg problem. > > And a popularity contest game as well. > > > > Without one click, you'll piss people off fast and they'll go look > elsewhere. Then you loose traction and that's bad. > > > > If I didn't had one click, I wouldn't have been learning as fast as I've > been. > > I agree with you. > > > Now I do have all pieces from different locations (even wanting to build > the VM on my own). > > > > For contrast, look at another community I am part of: Tiki Wiki CMS > Groupware. The system is topping SourceForge number of downloads, > committers, and is a general success for intranets in companies. > > > > Of course, the paradigm isn't pure at all, but easy enough to have a lot > of people contributing good stuff. > > > > We are at version 9 and I don't know any other package that is as > feature rich when it comes to the web. > > We are talking more than a million lines of code here. > > Now, we are moving further than one click: hosting providers provide a > full VM with everything installed for the stack. > > > > As of software developers, I do view 4 categories: > > > > - constructivists using established abstractions and not requiring > further exposure to inner workings of the system. They deliver business > value for common problems. > > - bridges understanding how the system works inside and are able to > convey usage patterns to the constructivists. They also feed back real > world usage problems to the next kind so that the system stays useful and > not pie in the skyish. > > - abstractionists: able to come up with a powerful set of abstractions > to solve a given problem in a general manner. Framework makers are here > > - technology makers: create core tech. Like a Cog-VM thing, CUDA, .. > > > > Try to pair types by jumping one strata and you are asking for trouble. > > > > Except for rare seasoned developers that are master of their craft and > are able to display behavioral flexibility. > > But these are a rare breed and you won't get them for a long time anyway > as these are seekers. > > I want a good installer for each platform :) > For newspeak there is a native installer for Mac OS and Windows. See http://www.squeakvm.org/svn/squeak/branches/Cog/nscogbuild/cygwinbuild/inst… http://www.squeakvm.org/svn/squeak/branches/Cog/nscogbuild/macbuild/install…. These allow one to install whatever one specifies using a native installer. The WIndows code is a little hairy and the Mac OS code is very simple. So if you consider a native installer a good introductory choice (it doesn't have to be the only one) then take a look. I can help with anyone trying to tailor to the WIndows installer. > And I want to let a chance to people to decide when they have to deal with > low level. > Pushing shit on their faces as a welcome message is not what we want. > > Now alex shipping cairo lib may be not be the best to do. It tooks some > time to compile on my machine > and it means some work to build the right libr for each sub platforms: 32, > 64â¦.. > > Now you can also use VW. :) For me this is simply no way. ;) > > Stef > > > > -- best, Eliot

March 30, 2012