[squeak-dev] [Pharo-dev] Pragma keyword / selector / methodSelector
astares at gmx.de
Mon Nov 14 19:18:26 UTC 2016
I was hit by this today already as it made Catalog slow like hell (which I fixed): https://pharo.fogbugz.com/f/cases/19342/.
+1 for the short-term revert
+10 for aligning Squeak and Pharo with a more intention revealing name
> Gesendet: Montag, 14. November 2016 um 19:49 Uhr
> Von: "Eliot Miranda" <eliot.miranda at gmail.com>
> An: "Pharo Development List" <pharo-dev at lists.pharo.org>
> Cc: squeak-dev at lists.squeakfoundation.org
> Betreff: Re: [Pharo-dev] Pragma keyword / selector / methodSelector
> Hi All,
> can I suggest that Pharo and Squeak coordinate on a change. First, #selector is bad because it is ambiguous. As already determined #keyword is awful because it's false (it is a message selector, not just a keyword). So could we
> - use #methodSelector and #pragmaSelector for the next few years, and deprecate #selector and #keyword?
> - after a suitable time use #selector to mean #pragmaSelector because that's the most useful abbreviation (in my experience I most often access #pragmaSelector)?
> _,,,^..^,,,_ (phone)
> > On Nov 14, 2016, at 6:37 AM, Esteban A. Maringolo <emaringolo at gmail.com> wrote:
> > 2016-11-14 11:27 GMT-03:00 phil at highoctane.be <phil at highoctane.be>:
> >> Breaking Metacello in Pharo 6: Not good. Revert: +1
> > Breaking Metacello in any version = Not good.
> > Metacello is very backward compatible but breaking pragma semantics
> > would require a rewrite of many configurations that work okay today
> > and would require a new version of Metacello that contemplates the new
> > selectors based on some criteria.
> > Regards!
> > Esteban A. Maringolo
More information about the Squeak-dev