Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Andrew Cagney <ac131313@ges.redhat.com>,
	Tom Tromey <tromey@redhat.com>,
	gdb-patches@sources.redhat.com,
	Fernando Nasser <fnasser@redhat.com>
Subject: Re: RFA: >, >>, and "tee" operators
Date: Tue, 13 Aug 2002 15:20:00 -0000	[thread overview]
Message-ID: <3D59847D.B30EE9CB@redhat.com> (raw)
In-Reply-To: <20020725031026.GA20117@nevyn.them.org>

Daniel Jacobowitz wrote:
> 
> GDB's option identifier varies, actually; symbol-file -readnow,
> add-symbol-file -s <section> <address> are the only two I see offhand.
> We only use / for print format characters.  Mostly we just drop them
> all on one line.
> 

That went in by mistake (it was before my time anyway).  Not that I have
anything against it (see below).

> Well, I don't have a problem with reserving / for FMT sequences
> (anything that modifies how output is printed) and - for options
> (anything that modifies what gets done).  I think '/' is only used for
> format sequences right now; at least I don't see anything otherwise in
> the manual besides display, print, and x.  Heck, I actually think
> separating format specifiers and options this way is intuitive.

That was exactly my argument years ago.  But I lost it (well, actually
the discussion went on and on for weeks without anyone reaching an
agreement and I gave up on the idea).


I don't see much problem in using the set commands (and thus avoinding
this issue).  It also has its advantages like a show comand.
Besides, set/show commands are there for things that alter GDB's 
behavior -- in the case, where output is sent.


What is the current option being defended?


-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


  parent reply	other threads:[~2002-08-13 22:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-23 11:51 Daniel Jacobowitz
2002-07-23 12:23 ` Tom Tromey
2002-07-23 13:18   ` Daniel Jacobowitz
2002-07-23 13:20     ` Tom Tromey
2002-07-23 13:58       ` Daniel Jacobowitz
2002-07-24 20:10         ` Andrew Cagney
2002-07-24 20:14           ` Daniel Jacobowitz
2002-07-25  9:17             ` Andrew Cagney
2002-07-25 10:36               ` Daniel Jacobowitz
2002-07-25 10:46                 ` Andrew Cagney
2002-07-30 13:00                   ` Daniel Jacobowitz
2002-07-30 20:36                     ` Andrew Cagney
2002-07-30 20:51                       ` Daniel Jacobowitz
2002-07-30 20:58                         ` Andrew Cagney
2002-07-30 22:45                           ` Daniel Jacobowitz
2002-07-31  9:36                       ` david carlton
2002-07-31  9:39                         ` Daniel Jacobowitz
2002-08-01  8:05                           ` Andrew Cagney
2002-08-01 10:24                             ` david carlton
2002-08-01 12:03                               ` Daniel Jacobowitz
2002-08-01 12:16                                 ` david carlton
2002-08-13 15:20             ` Fernando Nasser [this message]
2002-07-23 14:23       ` Grant Edwards
2002-07-24  1:59 ` Eli Zaretskii
2002-07-24 19:01 ` Andrew Cagney
2002-07-24 22:15   ` Daniel Jacobowitz

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=3D59847D.B30EE9CB@redhat.com \
    --to=fnasser@redhat.com \
    --cc=ac131313@ges.redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=tromey@redhat.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