On Tue, 29 May 2001 18:25:45 +0100 (BST), Dave Mitchell wrote:
>diffs:
>
>-"K&R" style for indenting control constructs
>+"K&R" style for indenting control constructs: ie the closing C<}> should
>+line up with the opening C<if> etc.
On Wed, 30 May 2001 10:37:06 -0400, Dan Sugalski wrote:
>I realize that no matter what style we choose, there will be a good crop of
>people who won't be thrilled with it. (For the record, we can count me as
>one, if that makes anyone feel any better :) That's inevitable.
If you have a diff/patching suite that falls over whitespace, you have a
problem with diff, not with style.
One can always to a pretty-print cleanup of the code, before doing the
diff, if all else fails.
IMO this is not worth bickering over.
--
Bart.
- PDD 2nd go: Conventions and Guidelines for Perl Source C... Dave Mitchell
- Re: PDD 2nd go: Conventions and Guidelines for Perl... Abhijit Menon-Sen
- Re: PDD 2nd go: Conventions and Guidelines for Perl... H . Merijn Brand
- Re: PDD 2nd go: Conventions and Guidelines for Perl... Bart Lateur
- Re: PDD 2nd go: Conventions and Guidelines for Perl... Dan Sugalski
- Re: PDD 2nd go: Conventions and Guidelines for Perl... Graham Barr
- Re: PDD 2nd go: Conventions and Guidelines for ... Dan Sugalski
- Re: PDD 2nd go: Conventions and Guidelines for Perl... Larry Wall
- Re: PDD 2nd go: Conventions and Guidelines for ... Dan Sugalski
- Re: PDD 2nd go: Conventions and Guidelines for ... Russ Allbery
- Re: PDD 2nd go: Conventions and Guidelines for Perl... H . Merijn Brand
- Re: PDD 2nd go: Conventions and Guidelines for Perl... Dave Mitchell
- Re: PDD 2nd go: Conventions and Guidelines for Perl... H . Merijn Brand
- Re: PDD 2nd go: Conventions and Guidelines for Perl... Graham Barr
