[ANSI-Smalltalk] Next STEPs

[Andres Valloud]

Paolo Bonzini wrote:

Andres Valloud wrote:

Bruce,

I think that another STEP for enhancements to make to the ANSI standard is
in order.  My motivation for this is that, over time, all the dialects have
accumulated convenience methods which more often than not one misses when a
different dialect is used.  An example of this would be
SequenceableCollection>>beginsWith: aSubSequence.  I am sure we can think of
others.


I agree a lot -- but you know that this is a *huge* can of worms? :-)


Yes.  On the other hand, not even considering what may easily be
standardized defeats the point of having a standard.  In other words, if
even something like SequenceableCollection>>beginsWith: is too difficult to
standardize, then exactly what are we going to be able to standardize?


For example, why #beginsWith: and not #startsWith: since all other methods
use "#startingAt:" for example?  And what about Stream>>#upToAll:?


Sure... if a consensus can be reached then great.  If not, we leave the one
for now and move on to the next.

 2) anyway, make sure that conflicting definitions in the dialects can be
worked around with Refactoring Browser rewritings.  I'm using them to port
Seaside and they work great.


Right, for example...

Andres.


On Thu, Mar 6, 2008 at 12:05 AM, Paolo Bonzini <bonzini at gnu.org> wrote:

> Andres Valloud wrote:
> > Bruce,
> >
> > I think that another STEP for enhancements to make to the ANSI standard
> > is in order.  My motivation for this is that, over time, all the
> > dialects have accumulated convenience methods which more often than not
> > one misses when a different dialect is used.  An example of this would
> > be SequenceableCollection>>beginsWith: aSubSequence.  I am sure we can
> > think of others.
>
> I agree a lot -- but you know that this is a *huge* can of worms? :-)
>
> For example, why #beginsWith: and not #startsWith: since all other
> methods use "#startingAt:" for example?  And what about Stream>>#upToAll:?
>
> IMHO what we should do is:
>
> 1) decide a source that wins if there are conflicts (unless there is
> consensus that the source is obsoleted by recent best practice).  I
> would vote for Dave N. Smith's Black Book.
>
> 2) anyway, make sure that conflicting definitions in the dialects can be
> worked around with Refactoring Browser rewritings.  I'm using them to
> port Seaside and they work great.
>
> Paolo
>
> _______________________________________________
> ANSI-Smalltalk mailing list
> ANSI-Smalltalk at lists.openskills.org
> http://lists.openskills.org/cgi-bin/mailman/listinfo/ansi-smalltalk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openskills.org/pipermail/ansi-smalltalk/attachments/20080306/dd725796/attachment.html