• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Where to report this clang issue?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Where to report this clang issue?


  • Subject: Re: Where to report this clang issue?
  • From: Jens Alfke <email@hidden>
  • Date: Thu, 13 Feb 2014 12:27:28 -0800


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?

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.

—Jens
 _______________________________________________
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

  • Follow-Ups:
    • Re: Where to report this clang issue?
      • From: Jean-Daniel Dupas <email@hidden>
References: 
 >Where to report this clang issue? (From: Matt Neuburg <email@hidden>)

  • Prev by Date: Where to report this clang issue?
  • Next by Date: Storyboard won't instantiate my class
  • Previous by thread: Where to report this clang issue?
  • Next by thread: Re: Where to report this clang issue?
  • Index(es):
    • Date
    • Thread