[cfe-dev] __APPLE_CC__ macro

[b17 c0de]

Well __APPLE_CC__ is also hard-coded to 6000 in the open-source clang
compiler. So it seems appropriate to ask what the point of this macro is
here.

On Sat, Jun 27, 2015 at 2:02 AM, Robinson, Paul <
Paul_Robinson at playstation.sony.com> wrote:

>  Questions about Apple products should be asked on an Apple forum.
> Sorry, this isn't the right place to ask.
>
> --paulr
>
>
>
> *From:* cfe-dev-bounces at cs.uiuc.edu [mailto:cfe-dev-bounces at cs.uiuc.edu] *On
> Behalf Of *b17 c0de
> *Sent:* Friday, June 26, 2015 3:53 PM
> *To:* cfe-dev Developers
> *Subject:* [cfe-dev] __APPLE_CC__ macro
>
>
>
> Can someone explain the usefulness of __APPLE_CC__? The documentation
> claims [the] macro is set to an integer that represents the version
> number of the compiler.
>
> But one version of Apple clang defines:
>
>
>
> #define __APPLE_CC__ 6000
>
> #define __apple_build_version__ 6020053
>
> #define __clang_version__ "6.1.0 (clang-602.0.53)"
>
>
>
>
>
> And another newer version of Apple clang defines:
>
> #define __APPLE_CC__ 6000
>
> #define __apple_build_version__ 7000053
>
> #define __clang_version__ "7.0.0 (clang-700.0.53.3)"
>
>
>
> So how does __APPLE_CC__ represent the "version" of the compiler? Is it
> stuck at 6000 now forever?
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20150627/f81e53c5/attachment.html>