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