public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Stallman <rms@gnu.org>
To: gdr@integrable-solutions.net
Cc: lopezibanez@gmail.com, bug-standards@gnu.org,
		gcc-patches@gcc.gnu.org, joseph@codesourcery.com
Subject: Re: error messages with ranges
Date: Sat, 17 Oct 2009 10:56:00 -0000	[thread overview]
Message-ID: <E1Mz6U2-0001f3-Iu@fencepost.gnu.org> (raw)
In-Reply-To: <206fcf960910160951v219b71fta98635ffaf6c136a@mail.gmail.com> 	(message from Gabriel Dos Reis on Fri, 16 Oct 2009 11:51:52 -0500)

    However, I would like you clarify the '::Argument locations:' marker.
    Do you intend the double colons '::' as token to introduce
    some form of meta data for tools? (In this case, it is to introduce
    locus, but is it an escape for more general tags?)

Yes, exactly.

I don't insist on using ::.  It was the first thing that occurred to me.
If someone has a better idea, let's use it.

  parent reply	other threads:[~2009-10-17 10:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6c33472e0910100443x70a568c3k2bd625de452d78da@mail.gmail.com>
2009-10-11 13:04 ` Manuel López-Ibáñez
2009-10-11 22:36   ` Karl Berry
2009-10-13  1:11   ` Karl Berry
2009-10-13 11:45     ` Manuel López-Ibáñez
2009-10-14  1:13       ` Richard Stallman
2009-10-14 11:53         ` Manuel López-Ibáñez
2009-10-15  7:07           ` Richard Stallman
2009-10-15 15:32             ` Manuel López-Ibáñez
2009-10-16  9:25               ` Richard Stallman
2009-10-16 16:54                 ` Gabriel Dos Reis
2009-10-16 20:46                   ` Chris Lattner
2009-10-16 21:31                     ` Joseph S. Myers
2009-10-16 21:31                       ` Gabriel Dos Reis
2009-10-18  3:10                       ` Richard Stallman
2009-10-18  8:51                     ` Richard Stallman
2009-10-17 10:56                   ` Richard Stallman [this message]
2009-10-17 10:59                 ` Manuel López-Ibáñez
2009-10-19  3:06                   ` Richard Stallman

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=E1Mz6U2-0001f3-Iu@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=bug-standards@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdr@integrable-solutions.net \
    --cc=joseph@codesourcery.com \
    --cc=lopezibanez@gmail.com \
    /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).