[Seaside-dev] Broken build because of use of #includesSubstring:

[Lukas Renggli]

I don't care much what version we use either. However we should keep
in mind that this is not about Pharo only, but also about all other
Seaside platforms.

Unfortunately ANSI does not describe a method for substring matching.
However ANSI describes #subStrings:, which would go along the current
#includesSubString: consistency wise.

Lukas



On 13 January 2013 22:11, Julian Fitzell <jfitzell at gmail.com> wrote:
> On Sat, Jan 12, 2013 at 10:42 PM, Sven Van Caekenberghe <sven at stfx.eu>
> wrote:
>>
>> Julian,
>>
>> On 12 Jan 2013, at 16:29, Julian Fitzell <jfitzell at gmail.com> wrote:
>> > No need for a grease-specific selector - just need different versions of
>> > grease for Pharo 1 and Pharo 2 if people want both versions of Pharo
>> > supported.. Can't recall what other platforms use, but in general I prefer
>> > 'Substring' myself.
>>
>> There are Grease-Pharo-[10|11|20]-Core packages in SqS/Seaside31 so I
>> guess the possibility to differentiate is there.
>>
>> My point is however that the Seaside developers have to make a simple
>> choice: keep the older #includesSubString: in the code base or switch to the
>> newer (more logical) #includesSubstring:
>>
>> Either choice is OK, just pick one so that we can get this trivial issue
>> out of the way.
>
>
> As I said, my personal preference is #includesSubstring: as "SubString" has
> always bothered me, but it depends what other platforms do. There's not much
> point using the version that only one platform uses and forcing all the
> others to implement a Grease extension...
>
> Julian
>
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>



-- 
Lukas Renggli
www.lukas-renggli.ch