-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/11/12 19:46, Mike Gilbert wrote: > On Sat, Nov 24, 2012 at 1:36 PM, Diego Elio Pettenò > <flamee...@flameeyes.eu> wrote: >> On 24/11/2012 10:19, Peter Stuge wrote: >>> Diego, remember the original point. It is obvious that a >>> common syntax is more coherent and thus easier for the world to >>> understand. Having that would be a good thing. It is also >>> obvious that the ruby syntax is problematic in the general >>> case. >> >> And the Ruby syntax has been devised to suit the _installed >> commands_ for the most part: ruby18 and ruby19 are _the commands >> you run_. >> > > I suppose we could use a hyphen like php does, but I don't think it > is worth the effort at this point. >
I would not mind changing to underscore if people really think it is worth the effort. It will certainly take some time to implement though. Maybe I could change the currently masked php5-5 slot to php5_5 instead and then eventually phase our the hyphen based slots. This would mean inconsistency between the php slots for some time, but eventual consistency with Python, which I do see as a good thing. - -- Ole Markus -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQEcBAEBAgAGBQJQsSS3AAoJEGurSuXEqSv14NIIAJtc6nbIIL504IZ8Vn77xaRC GQKRXRU2LUs3JbTTsedugad7XmuLvy/QRkwk+b5RDJFawXQAR0RhMi4H34mLw3fZ Am1uB34DuPWk4b+WvOfbxJdGH1wD73MemZBUr483K7RO2ejNmbEial3zhXlZGyKQ UAQ/X25/YAjQDJutXxbvA+q3oHaxGWYooTxniRYpQxszFmGeWefprUQT2ygCyO3h sxfyCapYx9/e2cuAVEuqddk6sqg2zqJI8TpzXWuAoetlZxbrfdhnXaGPrpnir7yc Zlqqtlk50Fac4d++gTbVen7Hz+eBOCQJQ7lkf6AWVBpI/vqKLlAoV0erDroOrwg= =CCx/ -----END PGP SIGNATURE-----
