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

[Julian Fitzell]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20130113/0405a070/attachment.htm