public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "karl at freefriends dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/51067] New: cpp.texi Line Control node not mentioning #, trailing integers
Date: Wed, 09 Nov 2011 19:45:00 -0000	[thread overview]
Message-ID: <bug-51067-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51067

             Bug #: 51067
           Summary: cpp.texi Line Control node not mentioning #, trailing
                    integers
    Classification: Unclassified
           Product: gcc
           Version: 4.6.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: preprocessor
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: karl@freefriends.org


In the Line Control node in cpp.texi, I do not see any mention of the
(long-used) form
# 1 "foo.c"
That is, # instead of #line.

Also, I do not see any description of the trailing integers now sometimes
present in the CPP output, as in:
# 1 "/usr/include/bits/sys_errlist.h" 1 3 4

(I looked around in the rest of the manual and other manuals too, to no avail. 
If the info is present elsewhere, at least an xref from Line Control would seem
useful.)

Thanks,
Karl


             reply	other threads:[~2011-11-09 19:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-09 19:45 karl at freefriends dot org [this message]
2011-11-09 20:14 ` [Bug preprocessor/51067] " joseph at codesourcery dot com
2011-11-09 20:17 ` pinskia at gcc dot gnu.org
2011-11-10  0:31 ` karl at freefriends dot org
2012-01-06  0:38 ` pinskia at gcc dot gnu.org
2012-01-06 22:44 ` karl at freefriends dot org

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=bug-51067-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).