public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: neil@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
	vil@rccp.tsukuba.ac.jp
Subject: Re: preprocessor/3858: fails to parse #include HASHDEFINEDMACROFORPATH"filename"
Date: Sat, 28 Jul 2001 14:23:00 -0000	[thread overview]
Message-ID: <20010728212304.22000.qmail@sourceware.cygnus.com> (raw)

Synopsis: fails to parse #include HASHDEFINEDMACROFORPATH"filename"

State-Changed-From-To: open->closed
State-Changed-By: neil
State-Changed-When: Sat Jul 28 14:23:04 2001
State-Changed-Why:
    Not a bug.  String concatenation occurs in the compiler after the standard preprocessing stages. In other words, the preprocessor does not do string
    concatenation.
    
    2.95.2 doing so could be construed as a bug or an undocumented feature.
    The evolution of GCC classifies it as a bug :-)  It is certainly not portable.
    
    As for no such file or directory, here it means "no such file" of course,
    but that's Unix for you.  Like CPP claimed, it ignored your final string
    as an excess token, and tried to open the directory as a file.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3858&database=gcc


             reply	other threads:[~2001-07-28 14:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-28 14:23 neil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-28 11:06 vil

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=20010728212304.22000.qmail@sourceware.cygnus.com \
    --to=neil@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=vil@rccp.tsukuba.ac.jp \
    /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).