all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: insert-header-preprocessor-definition
Date: Sun, 15 Apr 2018 01:54:49 +0200	[thread overview]
Message-ID: <86po317392.fsf@zoho.com> (raw)
In-Reply-To: 87y3htzclf.fsf@bsb.me.uk

Ben Bacarisse wrote:

> That is safe, yes. Doing it by hand, I think
> most people write H_COLOR [...] Actually,
> I like the symmetry

I like symmetry too but not for symmetry's
sake, so I removed the part that transformed
".h" into "_H" - which, ironically, I didn't
put there for the symmetry! Anyway now it is
just H_COLOR. [1]

Also, altho I've thought about this on and off
since I heard of it, I have failed to come to
terms with the underlying issue. How can
COLOR_H lead to an error when H_COLOR (or
H_COLOR_H) doesn't?

Because the syntax is the same, and all letters
are plain ASCII (the 2^7 table, where "_", the
underscore or "unit separator", is at number 95
counting from 0; see ascii(7)).

So there must be some fishy semantics going on.
Perhaps one needs to do a special study of the
C preprocessor? And if so, are there other
conventions one should be aware of?

And just what kind of error is it we're
trying (succeeding) to avoid?

[1] http://user.it.uu.se/~embe8573/emacs-init/ide/c-and-cpp.el

-- 
underground experts united
http://user.it.uu.se/~embe8573


  parent reply	other threads:[~2018-04-14 23:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <86fu429udy.fsf@zoho.com>
2018-04-11 15:47 ` insert-header-preprocessor-definition Ben Bacarisse
2018-04-11 20:41   ` insert-header-preprocessor-definition Emanuel Berg
2018-04-11 20:56     ` insert-header-preprocessor-definition Ben Bacarisse
2018-04-11 22:07       ` insert-header-preprocessor-definition Emanuel Berg
2018-04-14 23:54       ` Emanuel Berg [this message]
2018-04-15  1:02         ` insert-header-preprocessor-definition Ben Bacarisse
2018-04-15  7:44           ` insert-header-preprocessor-definition Yuri Khan
2018-04-15 19:35           ` insert-header-preprocessor-definition Emanuel Berg
2018-04-15 21:10             ` insert-header-preprocessor-definition Ben Bacarisse
2018-04-15 21:45               ` insert-header-preprocessor-definition Emanuel Berg
     [not found]           ` <mailman.12420.1523778312.27995.help-gnu-emacs@gnu.org>
2018-04-15 19:46             ` insert-header-preprocessor-definition Emanuel Berg
2018-04-16  5:35               ` insert-header-preprocessor-definition Yuri Khan
     [not found]               ` <mailman.12486.1523856961.27995.help-gnu-emacs@gnu.org>
2018-04-16  6:16                 ` insert-header-preprocessor-definition Emanuel Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86po317392.fsf@zoho.com \
    --to=moasen@zoho.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.