@interface and attributes

Clang Frontend
#1

Hi,

it’s

class attribute((visibility(“hidden”))) A {};

but

attribute((visibility(“hidden”))) @interface I @end

In the first case, clang emits a nice fixit if the attribute is written before the class keyword, while putting the attribute after @interface makes clang print an ugly diagnostic.

Instead of just making that print a nice fixit too, what do you think about allowing attributes for @interfaces after the @interface keyword too?

Nico

#2

I see no reason to introduce confusion about where to put attributes in an @interface. It's not like after the @interface is actually a good place to put attributes.

John.

#3

> it's
>
> class __attribute__((visibility("hidden"))) A {};
>
> but
>
> __attribute__((visibility("hidden"))) @interface I @end
>
> In the first case, clang emits a nice fixit if the attribute is written
before the class keyword, while putting the attribute after @interface
makes clang print an ugly diagnostic.
>
> Instead of just making that print a nice fixit too, what do you think
about allowing attributes for @interfaces after the @interface keyword too?

I see no reason to introduce confusion about where to put attributes in an
@interface. It's not like after the @interface is actually a good place to
put attributes.

Ok. The attached patch gives attributes after an objc directive a nicer
diagnostic then. Is this ok?

Nico

clang-objc-attrs.patch (4.64 KB)

#4

Ahy did you remove test/Parser/prefix-attributes.m test?
Other than that lgtm.

  • Fariborz
#5

Ahy did you remove test/Parser/prefix-attributes.m test?

I moved it to test/Parser/attributes.mm (since it now also tests postfix
attributes).

Other than that lgtm.

Thanks!