[GemStone-Smalltalk] first: / last:

[Bruce Badger via GemStone-Smalltalk]

This sounds like a candidate for Sport.  Sport already helps with the way
Gemstone streams are positioned, for example, so it should be possible to
handle this in a similar way.

Sent from my phone.  Please forgive brevity.
On 18 Sep 2014 16:58, "Richard Sargent via GemStone-Smalltalk" <
gemstone-smalltalk at lists.gemtalksystems.com> wrote:

> Gemstone/S mailing list wrote
> > The implementation of #first: and #last: in GemStone is very different
> > from VW, Pharo and VA.
> >
> > On GS the methods set the first or last value, in other dialects they
> > answer a copy with the first or last indexed values.
> >
> > ...
> >
> > Any plans for this to change?
>
> In general, no. We try to avoid breaking applications that are working for
> our customers by avoiding changes in APIs.
>
> Personally, I would like to change things to make GemStone more compatible
> with other dialects, but as indicated, there are cases where we would
> create
> problems we don't want.
>
> I have issues with the concepts behind #first, #first:, #last, and #last:,
> especially when compared to other API methods. In some respects, the
> GemStone implementation is more consistent. I think #copyFrist: and
> #copyLast: would be better and more accurate names for the functions and
> would avoid the semantic imprecision associated with #first: and #last:.
>
> Richard
>
>
>
>
> --
> View this message in context:
> http://forum.world.st/first-last-tp4778749p4778800.html
> Sent from the Gemstone/S mailing list archive at Nabble.com.
> _______________________________________________
> GemStone-Smalltalk mailing list
> GemStone-Smalltalk at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/gemstone-smalltalk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/gemstone-smalltalk/attachments/20140918/00b9c650/attachment.html>