Re: Attribute position in parsing class member function declarations
Sorry, I missed noticing your response.
I'm not sure what to do here. The Clang docs (http://clang-analyzer.llvm.org/annotations.html#attr_cf_returns_retained) note that as a Clang-specific attribute. Do you mean that we should put out a warning if some more strict standard mode is used, or that there should be a warning unless clang-specific attributes are explicitly enabled by some new option? Or should the test use some sort of "#if __has_feature(attribute_cf_returns_retained)" conditional? Or is the attribute not allowed after the function declation? Please instruct.
On Wed, Nov 25, 2009 at 4:09 PM, Douglas Gregor <[hidden email]> wrote:
On Nov 25, 2009, at 3:56 PM, John Thompson wrote:
I'm not sure this is optimal, but it seems to fix Bug 5605.
The parsing is fine, but this is missing some kind of diagnostic, because GCC rejects the test case: