After the indentation and line wrapping issues have been debated
ad nauseum, let's decide on the color of the bikeshed :) Purple?
http://purple.bikeshed.com/
--
Karl 2007-03-09 17:52
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://list
Hi,
On Sa, 2007-03-03 at 21:14 +1100, Chris wrote:
> To work with my system Fiesty libgoffice-0-3 0.3.5-1ubuntu1 I needed to
> change src/gnome-utils/gnc-html-graph-gog.c to use cairo.
> Attached is a patch I've wrapped these with HAVE_CAIRO. I've not
> attepted any automake foo the set HAVE_CAIRO
On Fri, 2007-03-09 at 15:46 -0500, Chris Shoemaker wrote:
> 2) encourage wrapping after the open parenthesis, e.g.:
>
> foo_is_a_short_name = but_these_names_are_rather_too_long(
> argument1, argument2, argument3, argument4);
>
> Do the ident settings permit 2)?
-nlp will tell ind
On Fri, Mar 09, 2007 at 10:16:47AM -0500, Josh Sled wrote:
> On Thu, 2007-03-08 at 23:46 -0500, David Hampton wrote:
> > -l80Line width of 80.
>
> This one I find problematic. I understand the arguments for it, and
> have made them myself. But identifiers and type names are just too long
Josh -
I completely agree that 80 won't cut it. I use 132 - why? - because I am old.
That was the standard for old printouts. Anyone remember "greenbar"?
Just for fun I followed your link and copied the code. Then I opened it in
emacs, xemacs, gedit, vim, and kate. Not a single line wrapped in
Josh Sled <[EMAIL PROTECTED]> writes:
> On Fri, 2007-03-09 at 11:00 -0500, Perry E. Metzger wrote:
>> You can rail against how stupid this is, but it won't get you very far
>> with those of us who live this way. You can thus choose to make the
>> code unreadable by a large chunk of the developer
On Fri, 2007-03-09 at 11:00 -0500, Perry E. Metzger wrote:
> You can rail against how stupid this is, but it won't get you very far
> with those of us who live this way. You can thus choose to make the
> code unreadable by a large chunk of the developer community, or stick
> to 80 columns.
I'm not
Josh Sled <[EMAIL PROTECTED]> writes:
> On Thu, 2007-03-08 at 23:46 -0500, David Hampton wrote:
>> -l80 Line width of 80.
>
> This one I find problematic. I understand the arguments for it, and
> have made them myself. But identifiers and type names are just too long
> these days. An 80-char li
On Fri, 2007-03-09 at 02:21 -0400, Peter Selinger wrote:
> I also recommend
>
> -T ExampleType
>
> for every 'typedef', so that you get:
:( We have nearly a thousand typedefs in the code some are relatively
anonymous, but most aren't... I wonder if there's a way to say '-T *',
or something si
On Fri, 2007-03-09 at 01:17 -0500, Chris Shoemaker wrote:
> I would recommend adding -ss, and I would have defaulted to -cli0,
> which is also K&R, but I don't feel strongly about it.
+1 on -ss .
--
...jsled
http://asynchronous.org/ - a=jsled;b=asynchronous.org; echo [EMAIL PROTECTED]
signatur
On Thu, 2007-03-08 at 23:46 -0500, David Hampton wrote:
> -l80 Line width of 80.
This one I find problematic. I understand the arguments for it, and
have made them myself. But identifiers and type names are just too long
these days. An 80-char limit can cause frequent and unnatural
line-breaki
11 matches
Mail list logo
