Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.c > #108484
| Subject | Re: Variable naming issue |
|---|---|
| Newsgroups | comp.lang.c |
| References | (5 earlier) <HdHLA.398274$2K7.326696@fx18.am4> <87efwgzlqj.fsf@bsb.me.uk> <87wpa82xp2.fsf@gmail.com> <Y_LLA.346164$sA1.224590@fx08.am4> <1d00eb7d-2881-4802-9c22-a23ba5aefe37@googlegroups.com> |
| From | bartc <bc@freeuk.com> |
| Message-ID | <HBMLA.2$NT.1@fx33.am4> (permalink) |
| Organization | virginmedia.com |
| Date | 2017-04-25 19:31 +0100 |
On 25/04/2017 19:19, David Kleinecke wrote: > The standard says the compiler tokenizes in translation phase 3 of > the pre-processor. After that it doesn't matter what the source > presentation looked like. Phases 1 and 2 are relatively trivial so > it would be fair to say that a compiler looses all dependence on the > appearance of the source immediately. > > The standard also describes what might be called one possible source > shape discipline. For any other isomorphic source (there is a one-to- > one mapping of external symbols) all one needs to do is to add a pre- > pre-processor that changes one's favorite source shape into the > standard's shape. > > For example one might write " AND "instead of "&&" and the pre-pre- > processor would change that to "&&". Yes, you can create a different syntax for the language /but you are still writing C/. > But I would prefer to roll phases 1 and 2 into 3 and simply modify the > tokenizer to accept my set of source "tokens". But there is a problem: suppose A writes a program using this new 'source shape', and wants to share it with B. What does A have to give B? If A was writing plain C, then just C source suffices. But now A has to provide extra tools to do this extra pre-processing. If B wants to read and maintain the program, then there is also the question of B having to understand this new syntax. (But maybe, when source already seems to rely on so much scripting anyway, that is outside of the language, this might not be that big a deal.) -- bartc
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