From: Andrew Cagney <ac131313@cygnus.com>
To: Michael Elizabeth Chastain <mec@shout.net>
Cc: gdb-patches@sources.redhat.com
Subject: Re: try_catch.cc -> try-catch.cc
Date: Wed, 29 May 2002 20:46:00 -0000 [thread overview]
Message-ID: <3CF59D43.4050201@cygnus.com> (raw)
In-Reply-To: <200205291708.g4TH81M02144@duracef.shout.net>
> I actually thought about that. :) I believe this section applies:
>
> http://sources.redhat.com/gdb/onlinedocs/gdbint_16.html#SEC157
> The source language programs do @emph{not} need to be in a consistent
> style. Since @value{GDBN} is used to debug programs written in many different
> styles, it's worth having a mix of styles in the testsuite; for
> instance, some @value{GDBN} bugs involving the display of source lines would
> never manifest themselves if the programs used GNU coding style
> uniformly.
>
> I know it's unlikely that gdb will ever have a bug where it can't
> handle '_' in a filename. (Although gdb does have filename completion).
> It's more the principle of keeping the test suite programs diverse
> and uncanonicalized.
(GDB will have bugs where it thinks try-catch.cc is `try - catch.cc' :-)
> I'll change it if you want it changed, though.
I see your point. I think here the question is more one of keeping the
test focused on exercising a specific feature - try/catch - rather than
a coding style issue.
Anyway, your call. (Hmm, we desperatly need some file name completer
tests including some containing spaces.)
enjoy,
Andrew
next prev parent reply other threads:[~2002-05-30 3:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 12:01 Michael Elizabeth Chastain
2002-05-29 20:46 ` Andrew Cagney [this message]
2002-05-30 1:42 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-05-29 22:00 Michael Elizabeth Chastain
2002-05-29 10:08 Andrew Cagney
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=3CF59D43.4050201@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mec@shout.net \
/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