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

SIXX on "large" files

by Sebastian Sastre

Hi guys, anyone here using SIXX? I'm having a consistent problem in opening a SixxReadStream on a file that has ~10MB of serialized objects. Smaller than that is all good Bigger, raises SixxXmlParseError ideas? Maybe I'm using the wrong version of XMLDOMParser? patches? workarounds? sebastian o/ PD: sixx was loaded with: Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSIXX'; load. (Smalltalk at: #ConfigurationOfSIXX) project latestVersion load.

Jan. 3, 2014

Re: [Pharo-dev] [Glass] printString and asString

by Martin McClure

On 01/03/2014 12:33 AM, Otto Behrens wrote: > Hi, > > I've run into one of my favorite problems in Smalltalk and decided to > try the list. Please don't shoot me on this one; perhaps you've run > into it yourself. If there are discussions that I should read, please > send me some info. Hi Otto, Well, you asked for comments. This is my personal opinion, which varies quite a bit from most implementations, since it's a bit 'old-school Smalltalk'. But I think the scheme below does fairly neatly distinguish the purposes of the various messages, which have gotten muddied over the years as new developers use the language somewhat differently. But maybe it was never the way I think I remember it being. :-) #printString and #printOn: These should answer a human-readable description of the receiver. The description does not need to include the class name, though it can. All objects should respond to these messages. Generally, #printString should be implemented in terms of #printOn: -- if you're writing to a stream you may not want to pay the cost of creating an extra string. #printString is the equivalent of other languages' toString(). #asString There should not be an Object>>asString. This message is *only* for converting string-like things to actual strings. So it would be implemented in String (to return self) and in Symbol, and *maybe* in things like ByteArray (where it does not *describe* the byte array, but answers a string whose characters have the values of the bytes). #storeString Produces legal Smalltalk source code that when executed will produce an equivalent object to the receiver. Needs to be implemented only for objects that can be specified as literals in Smalltalk syntax, but could probably be implemented for a few other simple objects. #displayString and so on. UI frameworks and applications will need to have their own ways of textually representing objects, so will add their own messages such as #displayString. The *only* messages that any application or framework can depend on *all* objects responding to are those that it defines itself, and #printString and #printOn:. Regards, -Martin

Jan. 3, 2014

Re: [Pharo-dev] A DateAndTime that does not understand #date or #time?

by Sebastian Sastre

Yeah Sven, I know timezones can be hell. Actually for me this isn't an issue as already ported my code with asDate and asTime. What worries me is the thinking behind that omission Why? Because you don't know where it will bite you next. But it will And it wont be intuitive On Jan 3, 2014, at 4:20 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I canât defend the API choice. > > But consider this: contrary to the name, a DateAndTime is much more that just a Date + a Time, it has a timezone offset and fractional seconds. That could be reason why there are #asDate and #asTime as conversion methods instead of #date and #time as accessors. On the other hand, there are lots of other accessors for all components. Maybe that is why #date and #time were not implemented: you would expect taking the date and time from a dateAndTime and composing them again would yield the original object, but that would not work. > > On 03 Jan 2014, at 19:03, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > >> yeah is what I'm using now but the 'as' means conversion while the #date and #time suggest delegating access to the other guy >> >> returning to the question.. is that omission intentional then? >> >> I mean.. >> >> There are counter intuitive things that are cool. >> >> This isn't one of those. >> >> This one sounds a lot against intuition for no good reason >> >> sebastian >> >> o/ >> >> >> >> >> >> On Jan 3, 2014, at 3:55 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >>> >>> On 03 Jan 2014, at 18:50, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: >>> >>>> How are we going to tell that our DateAndTime does not understand #date nor #time? (and keep our face straight) >>>> >>>> Sorry for the drama but hey... the raison d'Ãªtre, its meaning, the purpose in the life of a DateAndTime is to make you able to send messages about date and time :D >>>> >>>> How come that the most basic ones are being omitted? >>>> >>>> Am I missing something? >>> >>> #asDate and #asTime ? >>> >>>> sebastian >>>> >>>> o/ >>>> >>>> >>>> >>>> >>>> >>> >>> >> > >

Jan. 3, 2014

Re: [Pharo-dev] A DateAndTime that does not understand #date or #time?

by Sven Van Caekenberghe

I canât defend the API choice. But consider this: contrary to the name, a DateAndTime is much more that just a Date + a Time, it has a timezone offset and fractional seconds. That could be reason why there are #asDate and #asTime as conversion methods instead of #date and #time as accessors. On the other hand, there are lots of other accessors for all components. Maybe that is why #date and #time were not implemented: you would expect taking the date and time from a dateAndTime and composing them again would yield the original object, but that would not work. On 03 Jan 2014, at 19:03, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > yeah is what I'm using now but the 'as' means conversion while the #date and #time suggest delegating access to the other guy > > returning to the question.. is that omission intentional then? > > I mean.. > > There are counter intuitive things that are cool. > > This isn't one of those. > > This one sounds a lot against intuition for no good reason > > sebastian > > o/ > > > > > > On Jan 3, 2014, at 3:55 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> >> On 03 Jan 2014, at 18:50, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: >> >>> How are we going to tell that our DateAndTime does not understand #date nor #time? (and keep our face straight) >>> >>> Sorry for the drama but hey... the raison d'Ãªtre, its meaning, the purpose in the life of a DateAndTime is to make you able to send messages about date and time :D >>> >>> How come that the most basic ones are being omitted? >>> >>> Am I missing something? >> >> #asDate and #asTime ? >> >>> sebastian >>> >>> o/ >>> >>> >>> >>> >>> >> >> >

Jan. 3, 2014

Re: [Pharo-dev] A DateAndTime that does not understand #date or #time?

by Sebastian Sastre

On Jan 3, 2014, at 4:01 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > TimeStamp is on the way out since it hardly differs from DateAndTime and confuses the hell out of everyone. This discussion is independent of which name is best. I'm cool about keeping only one. Omitting the basics, breaking the most elemental intuitive expectations? not cool

Jan. 3, 2014

Re: [Pharo-dev] A DateAndTime that does not understand #date or #time?

by Sebastian Sastre

yeah is what I'm using now but the 'as' means conversion while the #date and #time suggest delegating access to the other guy returning to the question.. is that omission intentional then? I mean.. There are counter intuitive things that are cool. This isn't one of those. This one sounds a lot against intuition for no good reason sebastian o/ On Jan 3, 2014, at 3:55 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 03 Jan 2014, at 18:50, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > >> How are we going to tell that our DateAndTime does not understand #date nor #time? (and keep our face straight) >> >> Sorry for the drama but hey... the raison d'Ãªtre, its meaning, the purpose in the life of a DateAndTime is to make you able to send messages about date and time :D >> >> How come that the most basic ones are being omitted? >> >> Am I missing something? > > #asDate and #asTime ? > >> sebastian >> >> o/ >> >> >> >> >> > >

Jan. 3, 2014

Re: [Pharo-dev] A DateAndTime that does not understand #date or #time?

by Sven Van Caekenberghe

On 03 Jan 2014, at 18:57, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > BTW > > DateAndTime today class = DateAndTime. true > DateAndTime today asTimeStamp class = TimeStamp. true > DateAndTime today asTimeStamp asDateAndTime = DateAndTime. false (stays as TimeStamp) > > o.O And TimeStamp is on the way out since it hardly differs from DateAndTime and confuses the hell out of everyone. This discussion is independent of which name is best. > On Jan 3, 2014, at 3:50 PM, Sebastian Sastre <SEBASTIAN(a)FLOWINGCONCEPT.COM> wrote: > >> How are we going to tell that our DateAndTime does not understand #date nor #time? (and keep our face straight) >> >> Sorry for the drama but hey... the raison d'Ãªtre, its meaning, the purpose in the life of a DateAndTime is to make you able to send messages about date and time :D >> >> How come that the most basic ones are being omitted? >> >> Am I missing something? >> >> sebastian >> >> o/ >> >> >> >> >> >

Jan. 3, 2014

Re: [Pharo-dev] A DateAndTime that does not understand #date or #time?

by Sebastian Sastre

BTW DateAndTime today class = DateAndTime. true DateAndTime today asTimeStamp class = TimeStamp. true DateAndTime today asTimeStamp asDateAndTime = DateAndTime. false (stays as TimeStamp) o.O On Jan 3, 2014, at 3:50 PM, Sebastian Sastre <SEBASTIAN(a)FLOWINGCONCEPT.COM> wrote: > How are we going to tell that our DateAndTime does not understand #date nor #time? (and keep our face straight) > > Sorry for the drama but hey... the raison d'Ãªtre, its meaning, the purpose in the life of a DateAndTime is to make you able to send messages about date and time :D > > How come that the most basic ones are being omitted? > > Am I missing something? > > sebastian > > o/ > > > > >

Jan. 3, 2014

Re: [Pharo-dev] A DateAndTime that does not understand #date or #time?

by Sven Van Caekenberghe

On 03 Jan 2014, at 18:50, Sebastian Sastre <sebastian(a)flowingconcept.com> wrote: > How are we going to tell that our DateAndTime does not understand #date nor #time? (and keep our face straight) > > Sorry for the drama but hey... the raison d'Ãªtre, its meaning, the purpose in the life of a DateAndTime is to make you able to send messages about date and time :D > > How come that the most basic ones are being omitted? > > Am I missing something? #asDate and #asTime ? > sebastian > > o/ > > > > >

Jan. 3, 2014

Re: [Pharo-dev] out of scope for two weeks

by Tudor Girba

Good doctor. Smart patient :) Take care! Doru On Fri, Jan 3, 2014 at 5:10 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > hi guys > > my doc stopped me because Iâm exhausted so see you in two weeks. > > Stef > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 3, 2014