From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5691 invoked by alias); 30 May 2002 03:32:15 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 5649 invoked from network); 30 May 2002 03:32:10 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.240.27) by sources.redhat.com with SMTP; 30 May 2002 03:32:10 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id E5BAC3D48; Wed, 29 May 2002 23:32:19 -0400 (EDT) Message-ID: <3CF59D43.4050201@cygnus.com> Date: Wed, 29 May 2002 20:46:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0rc2) Gecko/20020518 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Michael Elizabeth Chastain Cc: gdb-patches@sources.redhat.com Subject: Re: try_catch.cc -> try-catch.cc References: <200205291708.g4TH81M02144@duracef.shout.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-05/txt/msg01018.txt.bz2 > 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