On 2001-05-29 18:25:45, [EMAIL PROTECTED] wrote: > > The following I<must> apply: > > =over 4 > > =item * > > 8-wide tabs > > =item * > > 4-wide indents for code, 2-wide indents for nested CPP #directives Please don't *require* the use of literal TABs (8 characters wide) to achieve 4-character indentation. In practice, this leads to ugly diffs and a completely unpredictable mixture of ^Is and spaces in the source. Either use 4 spaces everywhere, or use TABs for 8-character indentation (as the Linux kernel does). Please, don't mix the two. > Developer files > > For each source file (eg a F<foo.c> F<foo.h> pair), there should be an > accompanying developer file called F<foo.dev>. (Perhaps these .dev files should be /doc/devel/*.txt instead?) - ams
- 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