public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Russ Allbery <rra@stanford.edu>
To: gcc@gcc.gnu.org
Subject: Re: [patch] beginnings of the macro rewrite
Date: Mon, 24 Apr 2000 17:54:00 -0000	[thread overview]
Message-ID: <yl7ldnm24f.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <20000424115711.16845@cse.cygnus.com>

Michael Meissner <meissner@cygnus.com> writes:

> I know in the past perl 4.036 used it too, but I don't know if modern
> perl's currently use it.

It's still there:

     -P   causes your script to be run through the C preprocessor before
          compilation by Perl.  (Because both comments and cpp directives
          begin with the # character, you should avoid starting comments with
          any words recognized by the C preprocessor such as "if", "else", or
          "define".)

These days, it's mostly only used for very special applications and
obfuscated code, as the C preprocessor isn't really designed for
preprocessing other languages (some Perl constructs confuse it), and of
course Perl's use of # as a comment character conflicts pretty badly with
the use of the preprocessor.

-- 
Russ Allbery (rra@stanford.edu)             < http://www.eyrie.org/~eagle/ >

  reply	other threads:[~2000-04-24 17:54 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3900A36C.18989ED4@apple.com>
2000-04-21 17:17 ` Horst von Brand
2000-04-22 10:33   ` Zack Weinberg
2000-04-22 20:13     ` Marc Espie
2000-04-22 20:20     ` Neil Booth
2000-04-24  8:57     ` Michael Meissner
2000-04-24 17:54       ` Russ Allbery [this message]
2000-04-27 15:54     ` Philipp Thomas
2000-04-27 17:32       ` Joe Buck
2000-04-24 23:38   ` Martin Kahlert
2000-04-23  4:04 Richard Kenner
2002-07-04  9:55 C++ binary compatibility between GCC 3.1 and GCC 3.2? Andreas Jaeger
2002-07-04 10:23 ` H. J. Lu
2002-07-05 14:17 ` Mark Mitchell
2002-07-05 14:22   ` Andreas Jaeger
2002-07-05 14:28     ` Mark Mitchell
2002-07-05 14:53       ` David O'Brien
2002-07-05 15:08         ` Mark Mitchell
2002-07-06  5:34           ` Andreas Jaeger
2002-07-06  6:40             ` Gabriel Dos Reis
2002-07-06  6:40               ` Jakub Jelinek
2002-07-06  7:20                 ` Gabriel Dos Reis
2002-07-06  7:53                   ` Andreas Jaeger
2002-07-06  8:54                     ` Gabriel Dos Reis
2002-07-06 11:04                     ` Daniel Jacobowitz
2002-07-06  7:42                 ` Andreas Jaeger
2002-07-06 11:08                   ` Jeff Law
2002-07-06 11:10                     ` Gwenole Beauchesne
2002-07-06  6:19         ` Daniel Egger
2002-07-05 14:46   ` David O'Brien
2002-07-05 15:02     ` Mark Mitchell
2002-07-06  6:28       ` Scott Robert Ladd
2002-07-05 15:02     ` H. J. Lu
2002-07-05 15:12       ` David O'Brien
2002-07-05 15:20         ` H. J. Lu
2002-07-05 16:11           ` Stan Shebs
2002-07-05 16:12             ` David Edelsohn
2002-07-05 16:35               ` Stan Shebs
2002-07-05 22:18               ` Geoff Keating
2002-07-07 23:14               ` Mark Mitchell
2002-07-06  4:56     ` Andreas Jaeger
2002-07-06  6:44       ` Gerald Pfeifer
2002-07-06  7:35         ` Andreas Jaeger
2002-07-06 11:44         ` David O'Brien
2002-07-05 22:35 ` David Edelsohn
2002-07-06  5:40 ` Joseph S. Myers
2002-07-06  6:40   ` Gabriel Dos Reis
2002-07-06  7:49     ` Andreas Jaeger

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=yl7ldnm24f.fsf@windlord.stanford.edu \
    --to=rra@stanford.edu \
    --cc=gcc@gcc.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).