Issue 3459 in pharo: includesSubstring: aString caseSensitive: caseSensitive / includesSubString:

Status: Accepted
Owner: Benjamin.VanRyseghem.Pharo

New issue 3459 by Benjamin.VanRyseghem.Pharo: includesSubstring: aString  
caseSensitive: caseSensitive / includesSubString:
http://code.google.com/p/pharo/issues/detail?id=3459

Maybe one of this two methods should be changed in order to start as the  
other one


(includesSubstring: aString caseSensitive: caseSensitive have only 14  
senders ^^)

Comment #1 on issue 3459 by Benjamin.VanRyseghem.Pharo: includesSubstring:  
aString caseSensitive: caseSensitive / includesSubString:
http://code.google.com/p/pharo/issues/detail?id=3459

I'm talking about the selector of those methods

Updates:
        Labels: Milestone-1.3

Comment #2 on issue 3459 by stephane.ducasse: includesSubstring: aString  
caseSensitive: caseSensitive / includesSubString:
http://code.google.com/p/pharo/issues/detail?id=3459

Why do you want to have only one method? Having two is nice, you get a  
fallback. when you do not want to specify the case.

Comment #3 on issue 3459 by Benjamin.VanRyseghem.Pharo: includesSubstring:  
aString caseSensitive: caseSensitive / includesSubString:
http://code.google.com/p/pharo/issues/detail?id=3459

I do not want to have one method, but that both selector started the same  
way

one started by       includesSubstring:
and the other by   includesSubString:
                                                       ^

I think one of this selector should be changed ^^


PS : I hate too the shortcut on CMD+C to create a new entry !!!!!!!!