On Jan 5, 2009, at 7:56 AM, Lukas Renggli wrote:
>> I published to the inbox some cool collection extension methods that
>> we use all the time in Moose.
>> flatCollect:, collectAsSet:, and groupedBy:
>
> I think Squeak already has far too many of these methods. I would
> rather like to see them
Maybe the solution is to have a downloadable package
>>
>> Why can't we tag the methods with and build a tool that
>> check when you do a fill out.
>
> The problem is that such message sends can't be reliably detected
> statically.
You're right, but a fairly good approximation can be made.
Al
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
> Yes can you make a list of the ones that are conflicting with other
> implementations?
Well, unfortunately these are all methods that are not specified in
the ANSI standard.
>>> Why can't we tag the methods with and build a tool that
>>> check when you do a fill out.
>>
>> The problem is that
On Jan 6, 2009, at 8:04 AM, Lukas Renggli wrote:
>> So why do we do pharo. Really. If everything as to be compatible with
>> other smalltalk. Terrible.
>> Can't we get smarter?
>
> You are right, this change does not harm anyone not using the method.
>
> We'll have to update our tests of methods
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
i
> So why do we do pharo. Really. If everything as to be compatible with
> other smalltalk. Terrible.
> Can't we get smarter?
You are right, this change does not harm anyone not using the method.
We'll have to update our tests of methods not to be sent.
Still, I would rather like to see methods r
For me this is a problem of forces that do not easily resolve. If I
read the goals from the Pharo site
1...a clean and lean open-source Smalltalk platform, derived from Squeak
2...the obvious choice for professional Smalltalk development
3...an emerging platform to help people invent the future
for these methods I could provide extensions for VW with test.
I think that they are important. And I agree with Gary.
> Can't remember the number of times I've had to implement these kinds
> of
> generally useful methods on various Smalltalk dialects (particularly
> #groupedBy:, called it #cat
self anyOne.
> ^self allSatisfy: [:e | (aBlock value: e) = val]
>
> Regards, Gary.
>
> - Original Message -
> From: "Alexandre Bergel"
> To:
> Sent: Monday, January 05, 2009 6:02 PM
> Subject: Re: [Pharo-project] Collection extensions
>
>
>&
case."
|val|
self ifEmpty: [^true].
val := aBlock value: self anyOne.
^self allSatisfy: [:e | (aBlock value: e) = val]
Regards, Gary.
- Original Message -
From: "Alexandre Bergel"
To:
Sent: Monday, January 05, 2009 6:02 PM
Subject: Re: [Pharo-project] Collection extens
+ 1
On 5 Jan 2009, at 14:53, Gary Chambers wrote:
> Can't remember the number of times I've had to implement these kinds
> of
> generally useful methods on various Smalltalk dialects (particularly
> #groupedBy:, called it #categorizedBy: myself ;-) ). Really should
> be part
> of all Smalltal
Can't remember the number of times I've had to implement these kinds of
generally useful methods on various Smalltalk dialects (particularly
#groupedBy:, called it #categorizedBy: myself ;-) ). Really should be part
of all Smalltalks. I'd push for general adoption/standardisation for every
dial
Hi Stef,
Stéphane Ducasse wrote:
> So why do we do pharo. Really. If everything as to be compatible with
> other smalltalk. Terrible.
> Can't we get smarter?
> Why can't we tag the methods with and build a tool that
> check when you
> do a fill out. I do not write code to be portable to Visu
Maybe some lint rules could detect the usage of non portable methods...
Alexandre
On 5 Jan 2009, at 11:56, Lukas Renggli wrote:
>> I published to the inbox some cool collection extension methods that
>> we use all the time in Moose.
>> flatCollect:, collectAsSet:, and groupedBy:
>
> I think Squ
I vote to get these methods in.
Alexandre
On 5 Jan 2009, at 10:30, Stéphane Ducasse wrote:
> Hi all
>
> I published to the inbox some cool collection extension methods that
> we use all the time in Moose.
> flatCollect:, collectAsSet:, and groupedBy:
>
> http://code.google.com/p/pharo/issues/de
On Mon, Jan 5, 2009 at 3:06 PM, Stéphane Ducasse
wrote:
>
> On Jan 5, 2009, at 3:56 PM, Lukas Renggli wrote:
>
>>> I published to the inbox some cool collection extension methods that
>>> we use all the time in Moose.
>>> flatCollect:, collectAsSet:, and groupedBy:
>>
>> I think Squeak already has
On Jan 5, 2009, at 3:56 PM, Lukas Renggli wrote:
>> I published to the inbox some cool collection extension methods that
>> we use all the time in Moose.
>> flatCollect:, collectAsSet:, and groupedBy:
>
> I think Squeak already has far too many of these methods. I would
> rather like to see them
> I published to the inbox some cool collection extension methods that
> we use all the time in Moose.
> flatCollect:, collectAsSet:, and groupedBy:
I think Squeak already has far too many of these methods. I would
rather like to see them all removed, than new ones added. As an author
and maintain
Hi all
I published to the inbox some cool collection extension methods that
we use all the time in Moose.
flatCollect:, collectAsSet:, and groupedBy:
http://code.google.com/p/pharo/issues/detail?id=432&colspec=ID%20Type%20Status%20Summary&start=100
I would like to have your feedback because we
20 matches
Mail list logo
