From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: mode for preprocessed files
Date: Thu, 24 Jul 2008 08:52:31 -0400 [thread overview]
Message-ID: <jwvabg7e9cu.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <200807240300.m6O30OgU007933@sallyv1.ics.uci.edu> (Dan Nicolaescu's message of "Wed, 23 Jul 2008 20:00:23 -0700")
>> (it wouldn't have occurred
>> to me that those extensions are actually used for C and C++ files).
> They are the standard extensions that C/C++ compilers generate when you
> tell them to save the preprocessed file.
I know, but in all my years of C coding, I've never seen this
"feature" used. I've seen things piped through cpp, but not saved to
a .i(i) file.
> Compilers accept files with
> those extensions without wondering what the language is.
Of course, they don't need to wonder if it might be something completely
different since the mere fact of passing such a file to the compiler
already tells the compiler that it's some kind of source file, so at
worst the compiler has to decide which of the compiler's supported
source languages is used. Emacs has to take into account whether such
extensions are used in completely different contexts.
Stefan
PS: the .i and .ii extensions are not in Debian's /etc/mime.types, for example.
next prev parent reply other threads:[~2008-07-24 12:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 0:17 mode for preprocessed files Dan Nicolaescu
2008-07-24 2:24 ` Stefan Monnier
2008-07-24 3:00 ` Dan Nicolaescu
2008-07-24 12:52 ` Stefan Monnier [this message]
2008-07-24 14:14 ` Dan Nicolaescu
2008-07-24 21:09 ` Miles Bader
2008-07-24 22:05 ` Richard M Stallman
2008-07-24 2:30 ` David De La Harpe Golden
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=jwvabg7e9cu.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@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.