August 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] >>#next: SocketStream and other oddities

by Holger Hans Peter Freyther

On Sat, Aug 30, 2014 at 09:19:49AM +0200, stepharo wrote: > Hi holger Hi! thanks for the answer. > I got confused. sorry about that. > There is a problem with next: not raising error? Classic ReadStream in Pharo3.0 #[] readStream next: 2 => #[] SocketStream: 1.) Start something that listens to 12345 $ nc -l -p 12345 2.) In Pharo do | conn | conn := (SocketStream openConnectionToHostNamed: 'localhost' port: 12345) binary; noTimeout; yourself. [ (conn next: 4) inspect. ] on: ConnectionClosed do: [:e | "Never called" self halt ]. 3.) CTRL+C the netcat process.. 4.) In Pharo an inspector on an ByteArray is coming up. The ConnectionClosed signal is raised but swallowed by the SocketStream code. I don't know how realistic it is but I would appreciate if 1.) #[] readStream next: 4. Could raise an Error that one can not consume four bytes/elements. 2.) I understand that not raising "ConnectionClosed" is to allow a partial read from the socket. What is done in GNU Smalltalk is to at least signal an EndOfStream notificaton. So the socket code could read like: | conn | conn := (SocketStream openConnectionToHostNamed: 'localhost' port: 12345) binary; noTimeout; yourself. [ (conn next: 4) inspect. ] on: EndOfStream do: [:e | self handleClosing ]. is this more clear? holger

Aug. 30, 2014

Re: [Pharo-dev] ObjectLiterals thoughts....

by stepharo

For now parsetime as #() > Are you considering a form of compile-time expression or quasi-quotes? > > On 29 August 2014 11:35, stepharo <stepharo(a)free.fr> wrote: >> Hi guys >> >> we are looking at STON and ObjectLiterals with Christophe and for handling >> metadata. >> >> >> And I was brainstorming.... I was wondering if it would be possible to have >> a bit more use of self evaluating >> >> for example >> 1@3 >> #k -> 2 instead of (Association #k 123) >> >> >> my brainstorming is how could we minimize new syntactic constructs and still >> support a literal object format. >> So object literal cover that so may be this is good. >> >> 1@3 as (Point 1 3) >> and >> #k -> 123 as (Association #k 123) >> >> So I'm not clear but this is interesting to think about it. >> I would like to have also a dictionary literal syntax.... but this another >> story. >> >> Stef >> >> PS: Sven I added support for Association into the ObjectLiteral project to >> see how it works. >> >> >> >> >> >> >> >> >> >> 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 >> >> > >

Aug. 30, 2014

Re: [Pharo-dev] ObjectLiterals thoughts....

by stepharo

On 29/8/14 11:56, Sven Van Caekenberghe wrote: > Hi, > > I had a quick look at the ObjectLiterals project - I must admit that I forgot most about it ;-) me too :) Christophe was patching STON to make it less verbose when I remembered that igor sent some ideas around. > > Now that I see it again, one of the things that strikes me is that there is no such thing as a general object fallback, as far as I can see - that is a choice of course. > > Note that I did answer your earlier mail about STON > > http://forum.world.st/About-STON-td4772934.html > > Sven > > On 29 Aug 2014, at 11:35, stepharo <stepharo(a)free.fr> wrote: > >> Hi guys >> >> we are looking at STON and ObjectLiterals with Christophe and for handling metadata. >> >> >> And I was brainstorming.... I was wondering if it would be possible to have a bit more use of self evaluating >> >> for example >> 1@3 >> #k -> 2 instead of (Association #k 123) >> >> >> my brainstorming is how could we minimize new syntactic constructs and still support a literal object format. >> So object literal cover that so may be this is good. >> >> 1@3 as (Point 1 3) >> and >> #k -> 123 as (Association #k 123) >> >> So I'm not clear but this is interesting to think about it. >> I would like to have also a dictionary literal syntax.... but this another story. >> >> Stef >> >> PS: Sven I added support for Association into the ObjectLiteral project to see how it works. >> >> >> >> >> >> >> >> >> >> 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 >> >> > >

Aug. 30, 2014

Re: [Pharo-dev] ObjectLiterals thoughts....

by stepharo

>> Hey! >> >> Just for some "food for thought", you may want to read the parts under heading "Literal Smalltalk arrays" and the section following - "Sidestory: Adding literal Dictionaries to Smalltalk?" >> >> ...at: >> >> http://goran.krampe.se/2012/05/08/literal-arrays-vs-json-vs-ston-vs-tirade/ >> >> regards, GÃ¶ran > Yes, that is a good write up, touching on all kinds of aspects, balanced too. > Pretty complicated subject, right ? ;-) :) > As you mention it is quite hard to reach an agreement. > Objectives/goals are different for everybody. > > Since we had those discussions long ago, I've actually grown quite used to writing > > { #foo->1. #bar->2 } asDictionary #{ #foo->1. #bar->2 } could do it for literal ones :) > > I know it is not super efficient, or super compact, but I can certainly live with it.

Aug. 30, 2014

Re: [Pharo-dev] ObjectLiterals thoughts....

by stepharo

do you know if amber has { } because ideally I would love to have something like #() literl array ##() dynamic array why not :) #{} literal dictionary ##{} dynamic literal dictionary On 29/8/14 12:53, GÃ¶ran Krampe wrote: > Hey! > > Just for some "food for thought", you may want to read the parts under > heading "Literal Smalltalk arrays" and the section following - > "Sidestory: Adding literal Dictionaries to Smalltalk?" > > ...at: > > http://goran.krampe.se/2012/05/08/literal-arrays-vs-json-vs-ston-vs-tirade/ > > > regards, GÃ¶ran > >

Aug. 30, 2014

Re: [Pharo-dev] ObjectLiterals thoughts....

by stepharo

**thanks** I will reread it and add it to my folder. because one day I would love to have literal dictionary syntax and (I think that this is a pity that { } is already use for dynamic arrays. Stf On 29/8/14 12:53, GÃ¶ran Krampe wrote: > Hey! > > Just for some "food for thought", you may want to read the parts under > heading "Literal Smalltalk arrays" and the section following - > "Sidestory: Adding literal Dictionaries to Smalltalk?" > > ...at: > > http://goran.krampe.se/2012/05/08/literal-arrays-vs-json-vs-ston-vs-tirade/ > > > regards, GÃ¶ran > >

Aug. 30, 2014

Re: [Pharo-dev] >>#next: SocketStream and other oddities

by stepharo

Hi holger I got confused. There is a problem with next: not raising error? Stef On 29/8/14 09:16, Holger Hans Peter Freyther wrote: > Hi, > > while writing some SMS PDU parsing code I stumbled across an > "oddity" I have not seen with GNU Smalltalk. When calling the >>> #next: selector on a ReadStream and the number of elements > I need are not available, Pharo will return less or an empty > collection. This means I write code like this: > > | id len | > id := stream next: 4 > id size = 4 ifFalse: [^self reportError: 'Short read']. > > len := stream next: 4 > len size = 4 ifFalse: [^self reportError: 'Len not available']. > > > Besides the aesthetic issue it is getting worse when the SocketStream > class is in use. So now >>#next: 4 can return nil as well. But > naively I wrote code like this: > > > [ > | msg | > msg := ThingParser parse: aSocketStream. > ] on: ConnectionClosed do: [:e | > self logStuff: e. > self scheduleReconnect > ] > > > So to make the above code work with the SocketStream I need to > write the following. I had a quick look at why the ConnectionClosed > is swallowed and found the comment to allow partial reads out of > a dead socket. > > | id len | > id := stream next: 4. > id ifNil: [^self reportError: 'Short read']. > > len := stream next: 4 > len ifNil: [^self reportError: 'Short read']. > len size = 4 ifFalse: [^self reportError: 'Len not available'] > > > In GNU Smalltalk there is EndOfStream which is a subclass of > Notification and the above code boils down to: > > > [ > | id len | > id := stream next: 4. > len := stream next: 4. > ] on: EndOfStream do: [:e | > self logStuff: e. > self scheduleReconnect. > ]. > > > So couldn't the >>#readInto:startingAt:count: selector of SocketStream > do something like GNU Smalltalk and give an EndOfStream notification? > > > [self receiveData: anInteger] on: ConnectionClosed do:[:ex| > EndOfStream signalOn: self. > ex return > ]. > > > kind regards > holger > >

Aug. 30, 2014

Re: [Pharo-dev] Future of Spec

by stepharo

as far as I understand J is an APL like language so I was wondering with you do not have J binding inside pharo :) ? and script J from there? Stef On 29/8/14 21:15, Martin Saurer wrote: > Dear Stef, > Dear Pharo Community, > > Many thanks for answering my question about the future of Spec. > > What I have done for the J platform, and now will try to do for Pharo is not directly > comparable to Phobos (XULrunner) or Cocoa Widgets. At least I think so. > If you are interested please take a look at: http://www.jsoftware.com/jwiki/Scripts/qjide > > The qfe (Qooxdoo Frontend Engine) which is part of the qjide on the J platform is based > on the Ajax Framework "Qooxdoo" http://www.qooxdoo.org. > > The qfe is a JavaScript library which acts like Qt, WinForms, Cocoa, Morphic, etc. for the > desktop, but lives entirely in the web browser. > The web application itself is written in 100% J (now), or 100% Pharo (in the future). > To build a qfe based web application, there is no need to use HTML, CSS, XULrunner, etc. > The qfe may be bound to nearly any programming platform which has a web server. > Pharo together with the Zinc server is a great environment for creating web applications > that use a rich widget set like qfe provides. > > The final goal will be to create a Pharo GUI extension (probably based on Spec), where > applications can be opened like > MyGUIApp openInWorld. > or > MyGUIApp openInWeb. > > The first one opens a Spec (or Morphic) desktop GUI application in the Pharo window. > The second one serves the same application with (nearly) the same look-and-feel as a > web application. > > I will be happy to answer any questions on qfe. > > Cheers > > Martin > > >

Aug. 30, 2014

Re: [Pharo-dev] SqNumberParser and PGConnection in Pharo 3

by Esteban A. Maringolo

It could be #stable, I just was afraid of breaking somebody else stuff. I'm a champion at f*king up third parties repositories. :) Regards! Esteban A. Maringolo ps: There is also other versions of GLORP I didn't bless as #stable. 2014-08-29 17:17 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > On 19 May 2014, at 18:20, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > >> I commited PostgresV2-EstebanMaringolo.32 and >> ConfigurationOfPostgresV2-EstebanMaringolo.11 (added version 2.3) to >> SmalltalkHub. >> >> I hope it doesn't break anything. If so, please apologize. >> Esteban A. Maringolo > > Esteban, > > Is there any reason why we should not make this the #stable version, at least for Pharo ? Things do not work without your latest patch on Pharo 3. > > Sven > >> 2014-05-19 12:55 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> you are part of the team, so you have write access. >>> >>> Esteban >>> >>> On 19 May 2014, at 17:25, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>> >>>> I never uploaded the PostgresV2 update. And I don't see anybody else >>>> replaced the SqNumberParser to NumberParser reference. >>>> >>>> How can I upload the package back? >>>> Can I get write access to >>>> 'http://smalltalkhub.com/mc/DBXTalk/PostgresV2Driver/main' ? >>>> >>>> Regards, >>>> Esteban A. Maringolo >>>> >>>> >>>> 2014-04-10 11:19 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>>>> And you are in DBXTalk now >>>>> >>>>> On 10 Apr 2014, at 16:15, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>>>> >>>>>> I'm emaringolo@* :D >>>>>> >>>>>> Regards! >>>>>> >>>>>> Esteban A. Maringolo >>>>>> >>>>>> >>>>>> 2014-04-10 11:13 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>>>>>> >>>>>>> On 10 Apr 2014, at 16:08, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>>>>>> >>>>>>>> Can we coordinate efforts here? >>>>>>>> Can I at least have writing rights to GlorpDBX and PostgresV2 repos? :) >>>>>>> >>>>>>> What is your StHub username ? >>>>>>> I can add you to DBXTalk I think. >>>>>>> >>>>>> >>>>> >>>>> >>>> >>> >>> >> > >

Aug. 29, 2014

Re: [Pharo-dev] SqNumberParser and PGConnection in Pharo 3

by Sven Van Caekenberghe

On 19 May 2014, at 18:20, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > I commited PostgresV2-EstebanMaringolo.32 and > ConfigurationOfPostgresV2-EstebanMaringolo.11 (added version 2.3) to > SmalltalkHub. > > I hope it doesn't break anything. If so, please apologize. > Esteban A. Maringolo Esteban, Is there any reason why we should not make this the #stable version, at least for Pharo ? Things do not work without your latest patch on Pharo 3. Sven > 2014-05-19 12:55 GMT-03:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> you are part of the team, so you have write access. >> >> Esteban >> >> On 19 May 2014, at 17:25, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> >>> I never uploaded the PostgresV2 update. And I don't see anybody else >>> replaced the SqNumberParser to NumberParser reference. >>> >>> How can I upload the package back? >>> Can I get write access to >>> 'http://smalltalkhub.com/mc/DBXTalk/PostgresV2Driver/main' ? >>> >>> Regards, >>> Esteban A. Maringolo >>> >>> >>> 2014-04-10 11:19 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>>> And you are in DBXTalk now >>>> >>>> On 10 Apr 2014, at 16:15, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>>> >>>>> I'm emaringolo@* :D >>>>> >>>>> Regards! >>>>> >>>>> Esteban A. Maringolo >>>>> >>>>> >>>>> 2014-04-10 11:13 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >>>>>> >>>>>> On 10 Apr 2014, at 16:08, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>>>>> >>>>>>> Can we coordinate efforts here? >>>>>>> Can I at least have writing rights to GlorpDBX and PostgresV2 repos? :) >>>>>> >>>>>> What is your StHub username ? >>>>>> I can add you to DBXTalk I think. >>>>>> >>>>> >>>> >>>> >>> >> >> >

Aug. 29, 2014