Re: Positioning GCC_ATTR_DEPRECATED

[John W. Eaton]

On 12/29/2015 08:43 PM, LachlanA wrote:
> John W. Eaton wrote
> > Yeah, it does get kind of messy if we are writing things like
> >
> >     extern OCTAVE_ATTR_NORETURN OCTAVE_API void
> >     foobar (args, ...);
> >
> > or
> >
> >     extern OCTAVE_API void
> >     foobar (args, ...) OCTAVE_ATTR_NORETURN;
> >
> > I don't really see that one is better than the other.
>
> How about
>    extern OCTAVE_ATTR_NORETURN OCTAVE_API
>    void
>    foobar (args, ...);
>
> It is an extra line, but it stops the return type getting lost in the
> morass.

Writing them the way you suggest would be fine with me.  I'd just like 
to use a consistent style as that would be both easier to maintain and 
explain.

jwe