-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Marijn Schouten (hkBst) wrote:
> ý wrote:
>> Wulf C. Krueger schrieb:
>>> On Friday, 09. November 2007 10:10:42 Rený 'Necoro' Neumann wrote:
>>>> But as I think, that the uppercase version is the common behavior here,
>>>> it should not need this extra "PYTHON". :) That's why the patch ;)
>>> Actually, the mixed-case is what we have encountered in most cases. 
>>> Furthermore, as you stated correctly yourself, cmake is case-sensitive and 
>>> a patch that works around that fact only to have one parameter less for a 
>>> function doesn't really make much sense in my book.
>> Hmm ... ok - if you say, that more applications used the mixed case
>> versions, the current version is ok :)
>> I did not want to reduce one parameter, but when I first used this
>> eclass function, I assumed, that it will do the right thing (that is:
>> make it uppercase). It did not do so - that's why the patch ;).
> 
>> Another way would be to enhance the comment and state explicitly that it
>> takes the useflag literally and does not do any case transition :)
> 
> Please don't reuse other people's digital signatures, Necoro.

Never mind, I take it back.

Marijn

- --
Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML
<http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHNJ4Qp/VmCx0OL2wRAlNSAJwMzJyjMgcywE05LQSJIIvlZp8L5ACfUEnU
d0YFSB4eC7r+dHvVY1j4y9A=
=qJmh
-----END PGP SIGNATURE-----
-- 
[EMAIL PROTECTED] mailing list

Reply via email to