This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Name of files and functions etc.

From: David Pettersson <david_pettersson at bredband dot net>
To: gcc at gcc dot gnu dot org
Date: Wed, 30 Mar 2005 08:48:05 +0200
Subject: Re: Name of files and functions etc.
References: <424966F5.9050200@bredband.net> <m3is3ai7w2.fsf@localhost.localdomain> <87acomnttj.fsf@codesourcery.com>

Thanks for all the answers!

Usually the hardest part of programming is finding the right names for things, but good names cant be replaced by any amount of documentation.

By the way, how much changes should a patch contain in this case? As I understand the guidlines there should be one significant change per patch. Does this mean that cleaning the parse.y is one patch or that moving out all actions in parse.y that use pop_current_osb is one patch (my first goal)?

Is there any use doing this or are gcjx going to rule the world from tomorrow?

David

References:
- Name of files and functions etc.
  - From: David Pettersson
- Re: Name of files and functions etc.
  - From: Tom Tromey
- Re: Name of files and functions etc.
  - From: Zack Weinberg

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]