Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #108472
| Newsgroups | comp.lang.c |
|---|---|
| Date | 2017-04-25 07:12 -0700 |
| References | <daaca66f-c8ff-41f3-99b2-d4c457b96959@googlegroups.com> <YswLA.477560$UY3.417968@fx11.am4> <odmu6j$mg$1@dont-email.me> <OPELA.457019$5u1.273856@fx03.am4> <odnaf4$6gg$1@dont-email.me> |
| Message-ID | <6def3cb0-abdd-409c-980f-e35001bb4b3e@googlegroups.com> (permalink) |
| Subject | Re: Variable naming issue |
| From | supercat@casperkitty.com |
On Tuesday, April 25, 2017 at 6:07:27 AM UTC-5, David Brown wrote:
> Yes, an escape mechanism of some sort /could/ be used - but there are no
> forms of reserved identifiers that could sensibly be used, so there is
> nothing to stop conflict with other valid identifiers. You would have
> to have a silly long escape sequence - and that could conflict with
> length restrictions on assembly identifiers, and it would certainly look
> strange to anyone examining listing files, linker map files, etc., or
> using a debugger. And of course everything would fail if you tried to
> link these symbols with code generated with other tools.
Nothing would preclude a compiler from allowing the use of dollar signs in
macros or in symbols that are neither imported nor exported, no matter what
an assembler chose to do. As for imported/exported names, I think C would
have benefited from a qualifier or directive which would set the import/export
name for any symbol using a string literal, thus making it possible to e.g.
call an outside function named "restrict", and from a directive allowing any
character or characters which have no other meaning to be included within
the set that C will regard as identifier characters. Even if the latter
ability didn't apply to exported names, code could still say, e.g.
// Assuming a directive has indicated that $ should be allowed in macros
#define $foo DOLLAR_FOO
and then use $foo everywhere else.
Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Variable naming issue maximus fl <ajones2600@gmail.com> - 2017-04-24 16:17 -0700
Re: Variable naming issue David Kleinecke <dkleinecke@gmail.com> - 2017-04-24 16:28 -0700
Re: Variable naming issue bartc <bc@freeuk.com> - 2017-04-25 01:09 +0100
Re: Variable naming issue Noob <root@127.0.0.1> - 2017-04-25 09:37 +0200
Re: Variable naming issue bartc <bc@freeuk.com> - 2017-04-25 10:40 +0100
Re: Variable naming issue David Brown <david.brown@hesbynett.no> - 2017-04-25 13:07 +0200
Re: Variable naming issue bartc <bc@freeuk.com> - 2017-04-25 13:24 +0100
Re: Variable naming issue bartc <bc@freeuk.com> - 2017-04-25 13:27 +0100
Re: Variable naming issue Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-04-25 13:59 +0100
Re: Variable naming issue bartc <bc@freeuk.com> - 2017-04-25 14:20 +0100
Re: Variable naming issue Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-04-25 14:27 +0100
Re: Variable naming issue Keith Thompson <kst-u@mib.org> - 2017-04-25 11:52 -0700
Re: Variable naming issue Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-04-25 13:40 -0700
Re: Variable naming issue bartc <bc@freeuk.com> - 2017-04-25 22:14 +0100
Re: Variable naming issue David Brown <david.brown@hesbynett.no> - 2017-04-26 00:16 +0200
Re: Variable naming issue bartc <bc@freeuk.com> - 2017-04-26 00:13 +0100
Re: Variable naming issue David Brown <david.brown@hesbynett.no> - 2017-04-26 10:10 +0200
Re: Variable naming issue supercat@casperkitty.com - 2017-04-25 14:33 -0700
Re: Variable naming issue Malcolm McLean <malcolm.mclean5@btinternet.com> - 2017-04-25 06:39 -0700
Re: Variable naming issue Robert Wessel <robertwessel2@yahoo.com> - 2017-04-25 09:35 -0500
Re: Variable naming issue Gareth Owen <gwowen@gmail.com> - 2017-04-25 18:39 +0100
Re: Variable naming issue bartc <bc@freeuk.com> - 2017-04-25 18:49 +0100
Re: Variable naming issue David Kleinecke <dkleinecke@gmail.com> - 2017-04-25 11:19 -0700
Re: Variable naming issue bartc <bc@freeuk.com> - 2017-04-25 19:31 +0100
Re: Variable naming issue Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-04-25 23:36 +0100
Re: Variable naming issue David Kleinecke <dkleinecke@gmail.com> - 2017-04-25 17:04 -0700
Re: Variable naming issue Robert Wessel <robertwessel2@yahoo.com> - 2017-04-26 00:32 -0500
Re: Variable naming issue David Brown <david.brown@hesbynett.no> - 2017-04-25 16:02 +0200
Re: Variable naming issue Tim Rentsch <txr@alumni.caltech.edu> - 2017-05-02 05:25 -0700
Re: Variable naming issue supercat@casperkitty.com - 2017-05-02 10:04 -0700
Re: Variable naming issue Tim Rentsch <txr@alumni.caltech.edu> - 2017-05-05 03:06 -0700
Re: Variable naming issue supercat@casperkitty.com - 2017-04-25 07:12 -0700
Re: Variable naming issue Robert Wessel <robertwessel2@yahoo.com> - 2017-04-25 09:48 -0500
Re: Variable naming issue Robert Wessel <robertwessel2@yahoo.com> - 2017-04-25 09:52 -0500
Re: Variable naming issue Noob <root@127.0.0.1> - 2017-04-26 08:46 +0200
Re: Variable naming issue bartc <bc@freeuk.com> - 2017-04-26 11:46 +0100
Re: Variable naming issue bartc <bc@freeuk.com> - 2017-04-26 12:00 +0100
Re: Variable naming issue gordonb.o1c18@burditt.org (Gordon Burditt) - 2017-05-07 22:25 -0500
Re: Variable naming issue bartc <bc@freeuk.com> - 2017-05-08 10:35 +0100
Re: Variable naming issue bartc <bc@freeuk.com> - 2017-05-08 10:53 +0100
Re: Variable naming issue David Kleinecke <dkleinecke@gmail.com> - 2017-05-08 11:47 -0700
Re: Variable naming issue bartc <bc@freeuk.com> - 2017-05-08 19:59 +0100
Re: Variable naming issue gazelle@shell.xmission.com (Kenny McCormack) - 2017-04-25 10:43 +0000
Re: Variable naming issue Robert Wessel <robertwessel2@yahoo.com> - 2017-04-25 09:33 -0500
Re: Variable naming issue Keith Thompson <kst-u@mib.org> - 2017-04-24 17:26 -0700
Re: Variable naming issue maximus fl <ajones2600@gmail.com> - 2017-04-24 18:18 -0700
Re: Variable naming issue scott@slp53.sl.home (Scott Lurndal) - 2017-04-25 14:48 +0000
csiph-web