On Jan 6, 2009, at 9:45 AM, Oscar Nierstrasz wrote:
>
> Hi Folks,
>
> I recall some time ago discussing extensions like split: and join: for
> OrderedCollections to better support string operations typically
> supported in scripting languages. Maybe we need to take a deeper look
> at how best to refresh the Collections framework in Pharo to modernize
> it, yet without breaking the ANSI standard ...
Yes.
I would like that we move on this one too.
> There are a lot of good suggestions here, but since Collections are
> central to everything in Smalltalk, I think it would be wise if we
> step back and consider how best to proceed.
We started by writing tests tests and tests. The idea is to have
a good coverage of the collections and identify also the problems.
This is what we are currently doing.
We are writing traits and composing them to reuse tests across
multiple test case.
If you want to join you can publish in the pharoInbox.
I think that in the process we will then identify
misplaced/to remove method
> The issues appear to be:
>
> - stripping out obsolete junk
> - conformance to ANSI standard
> - traits refactoring
> - useful String extensions (based on similar interfaces in perl, Ruby
> etc.)
> - other useful collection extension (ditto)
>
> Did I miss something?
>
> We can't do all of these at once, but we do need to make progress ...
> What is the best way to go ahead?
Right now looking at the trait tests we implemented and improve them
(add more tests
add new trait tests and use the trait tests to better cover the system).
>
>
> - on
>
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
