For Grease, and therefore for Seaside, we agreed on the spelling includesSubString:.<div> <br clear="all"><div>John O'Keefe [|], CTO/Principal Smalltalk Architect, Instantiations Inc.<br>Skype: john_okeefe2 Mobile: +1 919 417-3181 (Business hours USA Eastern Time zone (GMT -5))<br>
<a href="mailto:john_okeefe@instantiations.com" target="_blank">john_okeefe@instantiations.com</a><br><a href="http://www.instantiations.com/" target="_blank">http://www.instantiations.com</a><br><em><strong>VA Smalltalk...Onward and Upward!</strong></em></div>
<br><br><div class="gmail_quote">On Sun, Jan 13, 2013 at 4:19 PM, Lukas Renggli <span dir="ltr"><<a href="mailto:renggli@gmail.com" target="_blank">renggli@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I don't care much what version we use either. However we should keep<br>
in mind that this is not about Pharo only, but also about all other<br>
Seaside platforms.<br>
<br>
Unfortunately ANSI does not describe a method for substring matching.<br>
However ANSI describes #subStrings:, which would go along the current<br>
#includesSubString: consistency wise.<br>
<br>
Lukas<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
On 13 January 2013 22:11, Julian Fitzell <<a href="mailto:jfitzell@gmail.com">jfitzell@gmail.com</a>> wrote:<br>
> On Sat, Jan 12, 2013 at 10:42 PM, Sven Van Caekenberghe <<a href="mailto:sven@stfx.eu">sven@stfx.eu</a>><br>
> wrote:<br>
>><br>
>> Julian,<br>
>><br>
>> On 12 Jan 2013, at 16:29, Julian Fitzell <<a href="mailto:jfitzell@gmail.com">jfitzell@gmail.com</a>> wrote:<br>
>> > No need for a grease-specific selector - just need different versions of<br>
>> > grease for Pharo 1 and Pharo 2 if people want both versions of Pharo<br>
>> > supported.. Can't recall what other platforms use, but in general I prefer<br>
>> > 'Substring' myself.<br>
>><br>
>> There are Grease-Pharo-[10|11|20]-Core packages in SqS/Seaside31 so I<br>
>> guess the possibility to differentiate is there.<br>
>><br>
>> My point is however that the Seaside developers have to make a simple<br>
>> choice: keep the older #includesSubString: in the code base or switch to the<br>
>> newer (more logical) #includesSubstring:<br>
>><br>
>> Either choice is OK, just pick one so that we can get this trivial issue<br>
>> out of the way.<br>
><br>
><br>
> As I said, my personal preference is #includesSubstring: as "SubString" has<br>
> always bothered me, but it depends what other platforms do. There's not much<br>
> point using the version that only one platform uses and forcing all the<br>
> others to implement a Grease extension...<br>
><br>
> Julian<br>
><br>
</div></div><div class="im HOEnZb">> _______________________________________________<br>
> seaside-dev mailing list<br>
> <a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
> <a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
><br>
<br>
<br>
<br>
</div><span class="HOEnZb"><font color="#888888">--<br>
Lukas Renggli<br>
<a href="http://www.lukas-renggli.ch" target="_blank">www.lukas-renggli.ch</a><br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
seaside-dev mailing list<br>
<a href="mailto:seaside-dev@lists.squeakfoundation.org">seaside-dev@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev" target="_blank">http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev</a><br>
</div></div></blockquote></div><br></div>