Re: Acceptable/Best formatting of callbacks (for pluggable storage)
От | Andres Freund |
---|---|
Тема | Re: Acceptable/Best formatting of callbacks (for pluggable storage) |
Дата | |
Msg-id | 20190111175832.ryyup5mci6atc3yy@alap3.anarazel.de обсуждение исходный текст |
Ответ на | Re: Acceptable/Best formatting of callbacks (for pluggable storage) (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
Hi, On 2019-01-11 09:42:19 -0500, Tom Lane wrote: > Andres Freund <andres@anarazel.de> writes: > > The pluggable storage patchset has a large struct full of callbacks, and > > a bunch of wrapper functions for calling those callbacks. While > > starting to polish the patchset, I tried to make the formatting nice. > > ... > > So, putting the parameter list, both in use and declaration, entirely > > into a new line yields decent formatting with pgindent. But it's kinda > > weird. I can't really come up with a better alternative, and after a > > few minutes it looks pretty reasonable. > > > Comments? Better alternatives? > > Use shorter method names? This sounds like an ugly workaround for > a carpal-tunnel-syndrome-inducing design. I'm confused. What did I write about that has unreasonably long names? And if you're referring to the wider design, that all seems fairly fundamental to something needing callbacks - not exactly a first in postgres. Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: