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

[Pharo-project] pharo-2.0-tests Â» win - Build # 428 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 21, 2012

[Pharo-project] Doits not logged to .changes file

by Igor Stasenko

just found that they are not logger.. is it known issue of i am lucky one (Pharo2.0a Latest update: #20267) (tried 20351 image, same story) -- Best regards, Igor Stasenko.

Oct. 21, 2012

Re: [Pharo-project] Parsing Smalltalk Array/Object Literals

by Igor Stasenko

On 21 October 2012 10:22, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Yes, something is wrong with the ObjectLiterals repository on SmalltalkHub, but I have no clue what. > > I made a copy in another place > > http://mc.stfx.eu/ObjectLiterals > hmm.. how i can download it? when i press a link in browser it asks me for username/password? > @Dale > > Of course ObjectLiteralsParser, is completely independent of any other code, that is the whole idea. > And it is very small as well, it should be portable to any Smalltalk. > > @Igor > > The Symbol and Number syntax accepted by ObjectLiteralsParser is artificially limited right now, as it was copied from STON. As long as it is a proper subset of Smalltalk that does not strike me as a problem. > > Anyway, the goal of the code is to allow for a more precise discussion. > i now modelling a system logger (to replace .changes file), and since i having no better idea, i'll try to use object literals for it. The idea is to preserve chunk format, but use object-literals for meta-information: logEntryExamples #(Method: ClassName instance "or class" 'category' 'author' (DateAndTime 'xxx') 'priorsourceId' ). #(TraitMethod: TraitName instance "or class" 'category' 'author' (DateAndTime 'xxx') 'priorsourceId' ). #(DoIt: 'author' (DateAndTime 'xxx') ). #(ClassComment: ClassName 'author' (DateAndTime 'xxx') 'priorsourceId' ). So, in log, it will look like: !#(Method: Object instance 'testing' 'Super Mario' (DateAndTime ' 2012-10-21T11:30:03.892+02:00') 'abra-ka-da-br-a' )! testSequenceIfNotEmptyDo self empty ifNotEmptyDo: [:s | self assert: false]. self assert: (self nonEmpty ifNotEmptyDo: [:s | self accessValuePutInOn: s]) = self valuePutIn ! ! Note the colon ':' in first literal. This is to prevent collision with any existing (and future) class name. As i suggested earlier, obj-literal can have name resolution logic in front of basic one - (Smalltalk at: name) and of course, there must be an extension mechanism, which can register own resolvers. I think it would be easy to extend chunk reading logic to detect that meta information stored as object-literal. Searching whole .sources file, i found only one occurrence of '!#' sequence and zero '!#(' If i do: '#( 1 2 3) yourself' in workspace, it writes: ! #(1 3 4 ) yourself! (an empty line between ! and #( ) -- Best regards, Igor Stasenko.

Oct. 21, 2012

[Pharo-project] [update 2.0] #20356

by Marcus Denker

Oct. 21, 2012

Re: [Pharo-project] Parsing Smalltalk Array/Object Literals

by Sven Van Caekenberghe

Yes, something is wrong with the ObjectLiterals repository on SmalltalkHub, but I have no clue what. I made a copy in another place http://mc.stfx.eu/ObjectLiterals @Dale Of course ObjectLiteralsParser, is completely independent of any other code, that is the whole idea. And it is very small as well, it should be portable to any Smalltalk. @Igor The Symbol and Number syntax accepted by ObjectLiteralsParser is artificially limited right now, as it was copied from STON. As long as it is a proper subset of Smalltalk that does not strike me as a problem. Anyway, the goal of the code is to allow for a more precise discussion. Sven On 21 Oct 2012, at 02:36, Igor Stasenko <siguctua(a)gmail.com> wrote: > Me too: > 'Could not load ObjectLiterals-SvenVanCaekenberghe.4.mcz: > ZnHttpUnsuccessful: 404 Not Found' > > however, the monticello repository window shows it is there. > > Nicolas, any clues what going on? -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

Oct. 21, 2012

Re: [Pharo-project] Parsing Smalltalk Array/Object Literals

by Igor Stasenko

Going via browser: http://smalltalkhub.com/#!/~SvenVanCaekenberghe/ObjectLiterals/versions/Obj… says "oops not found" On 21 October 2012 02:36, Igor Stasenko <siguctua(a)gmail.com> wrote: > Me too: > 'Could not load ObjectLiterals-SvenVanCaekenberghe.4.mcz: > ZnHttpUnsuccessful: 404 Not Found' > > however, the monticello repository window shows it is there. > > Nicolas, any clues what going on? > > On 21 October 2012 01:30, Dale Henrichs <dhenrich(a)vmware.com> wrote: >> Sven, >> >> For some reason I can't see any of the packages in your project on SmalltalkHub, but I was just curious if your work depends upon a pre-existing Smalltalk parser or not? >> >> I assume that "the JSON issue" will come up in a month or two again, so it is worth knowing the answer ahead of time:) >> >> Dale >> >> ----- Original Message ----- >> | From: "Sven Van Caekenberghe" <sven(a)stfx.eu> >> | To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr> >> | Sent: Saturday, October 20, 2012 11:51:34 AM >> | Subject: [Pharo-project] Parsing Smalltalk Array/Object Literals >> | >> | Hi, >> | >> | I took Igor's initial code and created a new project: >> | >> | http://smalltalkhub.com/#!/~SvenVanCaekenberghe/ObjectLiterals/ >> | >> | and I added ObjectLiteralParser to convert any Character Stream or >> | String into a Smalltalk Literal Array and eventually into an Object. >> | >> | This proof of concept moves the ObjectLiteral format/notation away >> | from the Smalltalk compiler and will help us discuss more concretely >> | the actual details of the specification (which is still not 100% >> | finished). >> | >> | I also added 12 unit tests and cleaned up the code and comments. >> | >> | Please have a look at the code. >> | >> | This is one of the tests: >> | >> | ObjectLiteralParserTests>>#testMixed1 >> | | input output | >> | input := ' >> | #(Array >> | 1 >> | foo >> | #''foo-#bar'' >> | true >> | false >> | nil >> | 3.14159 >> | -100 >> | ''string'' >> | (#OrderedCollection 7 8 9) >> | #(Set 10) >> | (Dictionary >> | x 1 >> | y 2) ) '. >> | output := { >> | 1. >> | #foo. >> | #'foo-#bar'. >> | true. >> | false. >> | nil. >> | 3.14159. >> | -100. >> | 'string'. >> | OrderedCollection withAll: #(7 8 9). >> | Set with: 10. >> | Dictionary newFromPairs: #(x 1 y 2 ). }. >> | self assert: (self parserOn: input) nextObjectLiteral equals: output >> | >> | I like this format, its simplicity and elegance is appealing, it >> | offers distinctive advantages in the Smalltalk context while its >> | slight readability disadvantage is acceptable. Like any format it is >> | a compromise and a tradeoff, but a rather good one. >> | >> | Regards, >> | >> | Sven >> | >> | -- >> | Sven Van Caekenberghe >> | http://stfx.eu >> | Smalltalk is the Red Pill >> | >> | >> | >> | >> | >> > > > > -- > Best regards, > Igor Stasenko. -- Best regards, Igor Stasenko.

Oct. 21, 2012

Re: [Pharo-project] Parsing Smalltalk Array/Object Literals

by Igor Stasenko

Me too: 'Could not load ObjectLiterals-SvenVanCaekenberghe.4.mcz: ZnHttpUnsuccessful: 404 Not Found' however, the monticello repository window shows it is there. Nicolas, any clues what going on? On 21 October 2012 01:30, Dale Henrichs <dhenrich(a)vmware.com> wrote: > Sven, > > For some reason I can't see any of the packages in your project on SmalltalkHub, but I was just curious if your work depends upon a pre-existing Smalltalk parser or not? > > I assume that "the JSON issue" will come up in a month or two again, so it is worth knowing the answer ahead of time:) > > Dale > > ----- Original Message ----- > | From: "Sven Van Caekenberghe" <sven(a)stfx.eu> > | To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr> > | Sent: Saturday, October 20, 2012 11:51:34 AM > | Subject: [Pharo-project] Parsing Smalltalk Array/Object Literals > | > | Hi, > | > | I took Igor's initial code and created a new project: > | > | http://smalltalkhub.com/#!/~SvenVanCaekenberghe/ObjectLiterals/ > | > | and I added ObjectLiteralParser to convert any Character Stream or > | String into a Smalltalk Literal Array and eventually into an Object. > | > | This proof of concept moves the ObjectLiteral format/notation away > | from the Smalltalk compiler and will help us discuss more concretely > | the actual details of the specification (which is still not 100% > | finished). > | > | I also added 12 unit tests and cleaned up the code and comments. > | > | Please have a look at the code. > | > | This is one of the tests: > | > | ObjectLiteralParserTests>>#testMixed1 > | | input output | > | input := ' > | #(Array > | 1 > | foo > | #''foo-#bar'' > | true > | false > | nil > | 3.14159 > | -100 > | ''string'' > | (#OrderedCollection 7 8 9) > | #(Set 10) > | (Dictionary > | x 1 > | y 2) ) '. > | output := { > | 1. > | #foo. > | #'foo-#bar'. > | true. > | false. > | nil. > | 3.14159. > | -100. > | 'string'. > | OrderedCollection withAll: #(7 8 9). > | Set with: 10. > | Dictionary newFromPairs: #(x 1 y 2 ). }. > | self assert: (self parserOn: input) nextObjectLiteral equals: output > | > | I like this format, its simplicity and elegance is appealing, it > | offers distinctive advantages in the Smalltalk context while its > | slight readability disadvantage is acceptable. Like any format it is > | a compromise and a tradeoff, but a rather good one. > | > | Regards, > | > | Sven > | > | -- > | Sven Van Caekenberghe > | http://stfx.eu > | Smalltalk is the Red Pill > | > | > | > | > | > -- Best regards, Igor Stasenko.

Oct. 21, 2012

Re: [Pharo-project] Parsing Smalltalk Array/Object Literals

by Dale Henrichs

Sven, For some reason I can't see any of the packages in your project on SmalltalkHub, but I was just curious if your work depends upon a pre-existing Smalltalk parser or not? I assume that "the JSON issue" will come up in a month or two again, so it is worth knowing the answer ahead of time:) Dale ----- Original Message ----- | From: "Sven Van Caekenberghe" <sven(a)stfx.eu> | To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr> | Sent: Saturday, October 20, 2012 11:51:34 AM | Subject: [Pharo-project] Parsing Smalltalk Array/Object Literals | | Hi, | | I took Igor's initial code and created a new project: | | http://smalltalkhub.com/#!/~SvenVanCaekenberghe/ObjectLiterals/ | | and I added ObjectLiteralParser to convert any Character Stream or | String into a Smalltalk Literal Array and eventually into an Object. | | This proof of concept moves the ObjectLiteral format/notation away | from the Smalltalk compiler and will help us discuss more concretely | the actual details of the specification (which is still not 100% | finished). | | I also added 12 unit tests and cleaned up the code and comments. | | Please have a look at the code. | | This is one of the tests: | | ObjectLiteralParserTests>>#testMixed1 | | input output | | input := ' | #(Array | 1 | foo | #''foo-#bar'' | true | false | nil | 3.14159 | -100 | ''string'' | (#OrderedCollection 7 8 9) | #(Set 10) | (Dictionary | x 1 | y 2) ) '. | output := { | 1. | #foo. | #'foo-#bar'. | true. | false. | nil. | 3.14159. | -100. | 'string'. | OrderedCollection withAll: #(7 8 9). | Set with: 10. | Dictionary newFromPairs: #(x 1 y 2 ). }. | self assert: (self parserOn: input) nextObjectLiteral equals: output | | I like this format, its simplicity and elegance is appealing, it | offers distinctive advantages in the Smalltalk context while its | slight readability disadvantage is acceptable. Like any format it is | a compromise and a tradeoff, but a rather good one. | | Regards, | | Sven | | -- | Sven Van Caekenberghe | http://stfx.eu | Smalltalk is the Red Pill | | | | |

Oct. 20, 2012

Re: [Pharo-project] Ring Methods and Traits...

by Camillo Bruni

Done: https://code.google.com/p/pharo/issues/detail?id=6618 On 2012-10-20, at 22:53, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > This is strange that we missed it. > Now veronica will be on vacation in November so we will see. > Can you create an issue so that I do not forget. > >> What's the plan there? >> >> We definitely need something like RGMethodDefinition>>#origin and certainly >> a proper implementation of RGMethodDefinition>>#isFromTrait. The current >> version will never work with remote methods as it relies 100% on >> CompiledMethod>>#isFromTrait >> >> best >> cami >> > >

Oct. 20, 2012

[Pharo-project] pharo-2.0-tests Â» win - Build # 427 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

Oct. 20, 2012