I don't like so much compatibility packages because people will not update their code and expect the compatibility package to always work. Why not just use what Marcus did for deprecations? Create a rule to transform ANSI Smalltalk to Pharo "magicly'? Le 3 sept. 2015 à 22:44, Gabriel Cotelli a écrit :
I've second Sven here. In case anybody wants the old method put it in some ANSICompatibility package to ease porting packages from ANSI-compliant Smalltalks.
On Thu, Sep 3, 2015 at 4:54 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote: We went through a lot of effort/pain to move to substring, I think for good reasons.
On 03 Sep 2015, at 21:31, Dimitris Chloupis <kilon.alios@gmail.com> wrote:
why not both ?
Because the proper English spelling is with lowercase
https://duckduckgo.com/?q=define%3A+substring&ia=definition
On Thu, Sep 3, 2015 at 9:45 PM stepharo <stepharo@free.fr> wrote: *) It appears that Pharo is removing subString: in favor of substring:. The ANSI standard defines subString:.
I was not aware of it. In fact ANSI is bad and totally incomplete (for example we studies strings and this is a mess and totally incomplete). Now we should probably add it. I will send the mail to the mailing-list and let people decide.