From mboxrd@z Thu Jan 1 00:00:00 1970 From: dave@horsfall.org (Dave Horsfall) Date: Mon, 15 May 2017 15:01:58 +1000 (EST) Subject: [TUHS] C declarations. In-Reply-To: <20170515045416.AF1CF124AEA4@mail.bitblocks.com> References: <015401d2caa0$79762650$6c6272f0$@ronnatalie.com> <68E8DC0A-D1B8-4FF0-AD26-ACDC57E308AF@pobox.com> <20170511223232.GM4341@mcvoy.com> <015b01d2caa7$c658c020$530a4060$@ronnatalie.com> <20170513012415.GZ4341@mcvoy.com> <025701d2cb92$ec8182a0$c58487e0$@ronnatalie.com> <20170513122050.GF9980@yeono.kjorling.se> <0CF82AC1-E835-4C06-813F-D9EFD2C12290@tfeb.org> <20170513124247.GG9980@yeono.kjorling.se> <57639684-050B-4995-859F-876CAFE4BE9C@serissa.com> <20170514042411.93CCB124AEA4@mail.bitblocks.com> <20170515045416.AF1CF124AEA4@mail.bitblocks.com> Message-ID: On Sun, 14 May 2017, Bakul Shah wrote: > > Nope. > > > > aneurin% cdecl > > Type `help' or `?' for help > > explain int*()* f > > syntax error > > declare f as ptr to function returning ptr to int > > int *(*f)() > > Sorry, I was less than clear. I was just doing a thought > experiment about an alternate declaration syntax. Requoting > from my email: Sorry - entirely my fault (which I'd realised just *after* I'd sent it, of course). Yes, your idea is a lot better. -- Dave Horsfall DTM (VK2KFU) "Those who don't understand security will suffer."