Re: Where to report this clang issue?
Re: Where to report this clang issue?
- Subject: Re: Where to report this clang issue?
- From: Matt Neuburg <email@hidden>
- Date: Thu, 13 Feb 2014 15:34:09 -0800
Okay, well, I've done my best. If they want to disregard my report that's their choice. m.
On Feb 13, 2014, at 2:57 PM, Jean-Daniel Dupas <email@hidden> wrote:
>
> Le 13 févr. 2014 à 21:27, Jens Alfke <email@hidden> a écrit :
>
>>
>> On Feb 13, 2014, at 11:52 AM, Matt Neuburg <email@hidden> wrote:
>>
>>> So what I'm left with is a desire to beg the clang developers to stop and go back, as the new version is breaking all kinds of stuff. How should I do that? I assume this is not directly an Xcode problem so the proper authority would not be Apple, but I'm unclear on the details. Thanks for any ideas - m.
>>
>> Did you file a bug report against clang?
>>
>
> Before filling a bug on clang, you have to make sure the bug can be reproduced with top of trunk clang build. Any report on an Apple's clang version will probably be discarded.
>
> If you don't want to bother to recompile the most recent version of clang and test with it, you should fill the bug on Apple Radar.
>
>> But if this were to manifest in some hypothetical pre-release of Xcode that we're not allowed to talk about on Apple's listserv, then in that purely fictional scenario you should file a bug report against Xcode too.
>>
--
matt neuburg, phd = email@hidden, http://www.apeth.net/matt/
pantes anthropoi tou eidenai oregontai phusei
Programming iOS 7! http://shop.oreilly.com/product/0636920031017.do
iOS 7 Fundamentals! http://shop.oreilly.com/product/0636920032465.do
RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
TidBITS, Mac news and reviews since 1990, http://www.tidbits.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden