Ciao,
i found some 'minor' things and i don't know as management ( report to the list ? ). I report in this e-mail for understand how to behave. 1) 10@5 *2 answer 20@10 but 2* ( 10@5 ) answer a MessageNotUnderstood occurred (error 2010), a Point does not understand #'_generality' 2) The class Time don't implementer the method : asDate asDate ^ Date today 3) The class Integer don't implementer the method: printStringHex printStringHex "returns the hex digit part of the integer when printed in hexadecimal format. 30 printStringHex '1E' 30 hex '16r1E' " ^self printStringBase: 16 4) Gemstone don't implement a Timespan subclass Date as into Pharo Instances of Date are Timespans with duration of 1 day. I don't find any equivalent class into Gemstone. Thanks for any considerations. Dario _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
> On Dec 1, 2014, at 8:12 AM, Dario Trussardi via Glass <[hidden email]> wrote:
> > 4) Gemstone don't implement a Timespan subclass Date as into Pharo > > Instances of Date are Timespans with duration of 1 day. > > I don't find any equivalent class into Gemstone. See Duration (as defined in ANSI). _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Administrator
|
In reply to this post by GLASS mailing list
Hi Dario, I think Time>>#asDate is just plain wrong. In the first case, it is not a conversion operation such as you get when you ask an object for its string representation or the converse. But worse, I don't think a Time should have a concept of which Date it is. Consider how silly Dollar>>#asPocket would be. Rather than add this construct to GLASS, I would advocate removing it from Pharo. |
In reply to this post by GLASS mailing list
Thanks James, >> On Dec 1, 2014, at 8:12 AM, Dario Trussardi via Glass <[hidden email]> wrote: >> >> 4) Gemstone don't implement a Timespan subclass Date as into Pharo >> >> Instances of Date are Timespans with duration of 1 day. >> >> I don't find any equivalent class into Gemstone. > > See Duration (as defined in ANSI). but Durations ( if right understand ) don't define a reference data when itself starting. With this limitations a need to manage two element: 1) the reference data 2) the duration Into Pharo i can operate with only one element which defines both the departure date that the duration. It's very useful when i need to select some element according to the period of membership. As advice to proceed to handle this problem? I do not want to invent the hot water Thanks for any considerations ? Dario _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
I see the distinction now. My inclination is to stay as close to ANSI as possible, so it seems that a new object with a Date and a Duration is what you need. I suppose it could be named Timespan and the API could be copied from Pharo. If it were popular it could be added to the GemStone portability layer.
> On Dec 1, 2014, at 9:01 AM, Dario Trussardi via Glass <[hidden email]> wrote: > > > Thanks James, > > >>> On Dec 1, 2014, at 8:12 AM, Dario Trussardi via Glass <[hidden email]> wrote: >>> >>> 4) Gemstone don't implement a Timespan subclass Date as into Pharo >>> >>> Instances of Date are Timespans with duration of 1 day. >>> >>> I don't find any equivalent class into Gemstone. >> >> See Duration (as defined in ANSI). > > but Durations ( if right understand ) don't define a reference data when itself starting. > > With this limitations a need to manage two element: > > 1) the reference data > > 2) the duration > > Into Pharo i can operate with only one element which defines both the departure date that the duration. > > It's very useful when i need to select some element according to the period of membership. > > As advice to proceed to handle this problem? > > I do not want to invent the hot water > > Thanks for any considerations ? > > Dario > > _______________________________________________ > Glass mailing list > [hidden email] > http://lists.gemtalksystems.com/mailman/listinfo/glass _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
In reply to this post by GLASS mailing list
Could you submit individual issues against the GsDevKit/GsDevKit project[1] for these? I am laying the groundwork for changing the name of GLASS to GsDevKit and I've already moved the glassdb/glass project to the GsDevKit/GsDevKit project so the issues are managed there, but I'm not quite ready to make the switch, so ongoing development is taking place in glassdb/glass (to be merged into GsDevKit when it's time)... Anyway, I would like to encourage folks to report bugs/issues using GitHub, since that's where the real work will happen. I don't want to discourage discussion, but the discussion that you and James had about the Timespan should have taken place on the TimeSpan issue, so that whoever comes along to do the actual work would have the benefit of seeing your interchange and possibly contributing and adding to it ... As it stands this discussion will fade over time and it can be difficult to recover the conversation thread as time goes by ... Perhaps bug reports should start with a github issue report followed by a message to this list referencing the issue number ... then any follow-on conversation can take place on the specific issue ... Dale On Mon, Dec 1, 2014 at 8:12 AM, Dario Trussardi via Glass <[hidden email]> wrote: Ciao, _______________________________________________ Glass mailing list [hidden email] http://lists.gemtalksystems.com/mailman/listinfo/glass |
Free forum by Nabble | Edit this page |