This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [rfa/testsuite] more tests in gdb.c++/m-static
- From: David Carlton <carlton at math dot stanford dot edu>
- To: Daniel Jacobowitz <drow at mvista dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Cc: carlton at math dot stanford dot edu
- Date: 16 Aug 2002 14:37:06 -0700
- Subject: Re: [rfa/testsuite] more tests in gdb.c++/m-static
- References: <ro1fzxewlg8.fsf@jackfruit.Stanford.EDU><20020816213122.GA12044@nevyn.them.org>
In article <20020816213122.GA12044@nevyn.them.org>, Daniel Jacobowitz <drow@mvista.com> writes:
> On Fri, Aug 16, 2002 at 02:19:35PM -0700, David Carlton wrote:
>> * What's the convention for submitting new files (as opposed to
>> patches to existing files)? (I'd look through the mail archive for
>> examples, but I don't seem to be able to access it right now.) I'm
>> attaching them below as files and hoping that the mailer will make
>> it clear what they're named and so forth; please let me know if I
>> should do anything else.
> I usually use diff -N to do this.
Makes sense.
> Oh, and you might want to use namespace names that aren't in the
> implementation space (__gnu is in the implementation space, because
> it starts with two underscores. _[A-Z] is also reserved.)
Thanks for the tip. I inherited that from the pre-existing
m-static.cc file; to be honest, I have no idea why that file uses
namespaces at all, let alone namespaces beginning with two
underscores. But if I add more tests myself, I'll make sure to avoid
such underscores.
David Carlton
carlton@math.stanford.edu