[cfe-dev] *** GMX Spamverdacht *** Re: Recognize CC and clang-CC?

Alp Toker alp at nuanti.com
Sun Nov 10 03:37:29 PST 2013


On 10/11/2013 10:27, Sebastian Redl wrote:
> On Nov 9, 2013, at 16:17, Hal Finkel wrote:
>
>> ----- Original Message -----
>>> On Thu, Nov 7, 2013 at 12:46 PM, Joerg Sonnenberger
>>> <joerg at britannica.bec.de> wrote:
>>>> On Thu, Nov 07, 2013 at 12:27:13PM -0500, Zhihao Yuan wrote:
>>>>> The upper case CC is a traditional UNIX naming of
>>>>> C++ compiler.  BSDs follow this, and cmake regards
>>>>> it as the host C++ compiler as well.
>>>> NetBSD doesn't. I'm moderately sure OpenBSD and DragonFly don't
>>>> either.
>>>> Frankly, I don't know what tradition outside FreeBSD you are
>>>> talking
>>>> about -- pretty much everyone has been using "c++" as canonical
>>>> name for
>>>> the C++ compiler for ages.
>>> I'm sorry I should not mention "BSDs".  To my best knowledge, Solaris
>>> has CC command and it's still their official way to invoke C++
>>> compiler.
>>> FreeBSD may be influenced by that.
>> Does anyone see any harm in adding 'CC' to the list of C++ aliases?
> What about a Windows user who names it CC.EXE? The case insensitivity means that there's no difference between that and cc.exe.

Not just Windows. The default filesystem on Mac OS X is also
case-insensitive (but case aware):

$ cLaNg
clang: error: no input files

Alp.

> (I don't think doing that is sensible. I'm just curious what would happen.)
>
> Sebastian
> _______________________________________________
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev

-- 
http://www.nuanti.com
the browser experts




More information about the cfe-dev mailing list