Not to hijack this thread but just noticed that piecesCutWhere: is implemented in Collection under Pharo and under SequencableCollection under Squeak. Need to check against latest Pharo3 but this should be changed in Pharo as piecesCutWhere: implementation depends on object being of type SequencableCollection.
Cheers Carlo On 25 Feb 2014, at 12:47 AM, Norbert Hartl <[email protected]> wrote: Am 24.02.2014 um 23:09 schrieb Eliot Miranda <[email protected]>: > > > > On Mon, Feb 24, 2014 at 1:58 PM, Norbert Hartl <[email protected]> wrote: > > Am 24.02.2014 um 22:19 schrieb Eliot Miranda <[email protected]>: > >> >> >> >> On Mon, Feb 24, 2014 at 12:29 PM, Alexandre Bergel<[email protected]> >> wrote: >> Would be great to have: ‘ConfigurationOfRoassal’ chopCamel => >> #(‘Configuration’ ‘Of’ ‘Roassal’). >> >> 'ConfigurationOfRoassal' piecesCutWhere: [:a :b| a isLowercase and: [b >> isUppercase]] an OrderedCollection('Configuration' 'Of' 'Roassal') >> >> It's too trivial, surely. >> > No it is not. Because you have to know about it. Thanks for that one. > > "I learned something today[tm]“ > > But the real things to learn are the Method Finder and the browser. Adding a > lot of names that are known to those that know some scripting language du > jour, but are incomprehensible to me, and no doubt many others, is not doing > anything for anybody, except trying to be pointlessly cool. Trying to > encourage programmers to use the ability of the system to self-introspect and > self-document is giving them general skills they can build upon. So a > project to improve the UI so that programmers are led to tools they can use > for discovery seems worth-while to me, while adding yet more short-hand to > hand-hold the ignorant isn't helping, IMHO. > I agree that adding a lot of names is not helping because that might be the reason I didn’t know that selector. What kind of selectors are the right ones I’m not the one to judge. But to be honest if I think about a collection the selector #piecesCutWhere: is not intuitive to me, too. So I’m glad you brought that to my attention. thanks again, Norbert > > Norbert > >> >> Alexandre >> >> >> On Feb 24, 2014, at 2:30 PM, Daniela Meneses <[email protected]> wrote: >> >> > Hi to all, >> > >> > As you may know I'm working on in some improvements for the String class. >> > Until now I implemented some missing tests. Right now I'm looking forward >> > to add new methods that could be useful based on Ruby API >> > (http://www.ruby-doc.org/core-2.1.0/String.html). These are a few of the >> > methods that I'm planning to implement: >> > >> > • chomp(separator=$/) -> new_str >> > • chop() -> new_str >> > • ljust(integer, padstr='') ->new_str >> > • next -> new_str >> > • partition(sep) -> [head, sep, tail] >> > >> > Could you help to find out if these methods are already available for the >> > String class? >> > >> > If you have any idea of new methods for the string class, will be really >> > welcome. >> > >> > -- >> > Cheers, >> > Daniela Meneses >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >> -- >> best, >> Eliot > > > > > -- > best, > Eliot
