Re: try_catch.cc -> try-catch.cc

[Daniel Jacobowitz <drow at mvista dot com>]

On Wed, May 29, 2002 at 11:32:19PM -0400, Andrew Cagney wrote:
> >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.)

I don't think CVS will let us get away with that, and I'm even more
sure djgpp will gripe.  We'd need to create them at testsuite time,
which is tricky...

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer