Messages in this thread | | | Subject | Re: [RFC: Coding Style] Best way to split a long function declaration with modifiers | From | Joe Perches <> | Date | Sat, 12 May 2018 08:41:31 -0700 |
| |
On Sat, 2018-05-12 at 18:19 +0300, Igor Stoppa wrote: > I have been wondering if it's ok to break a long (function declaration) > line in the following way: > > static __always_inline > struct foo_bar *__get_foo_bar(type1 parm1, type2 parm2, type3 parm3) > > > instead of: > > static __always_inline struct foo_bar *__get_foo_bar(type1 parm1, > type2 parm2, > type3 parm3) >
I think so.
> I personally like more the former, not to mention that it uses also one > line less, but it seems less common in the sources. > The coding style references do not seem to say anything explicit about > which style to prefer.
I think the first style should be preferred when the combined character length of <type> <function_name> is relatively long.
| |