At 1141671548, Miles Bader wrote:
> If you attempted to view such code using an application
> which uses the standard tab size of 8 -- e.g., more or
> less in a terminal -- blocks would end up being indented
> by _16 spaces per block level_, which is (pardon my
> french) pretty fucking absurd.
Ind
On Mon, 6 Mar 2006, Hendrik Sattler wrote:
Can you explain that?
Either the '{' and '}' are one indentation level down or the same indentation
level.
Hah! Not in GNU.
The GNU coding standards want you to indent '{' and '}' x/2 spaces, while
the code inside is indented x. So, the result is:
Am Montag, 6. März 2006 11:39 schrieb Hendrik Sattler:
> 8bit tab width
s/8bit/8 spaces/
me is confused
HS
pgpWd6uTc4ZU0.pgp
Description: PGP signature
Am Montag, 6. März 2006 10:59 schrieb Miles Bader:
> If you attempted to view such code using an application which uses the
> standard tab size of 8 -- e.g., more or less in a terminal -- blocks
> would end up being indented by _16 spaces per block level_, which is
> (pardon my french) pretty fucki
Hendrik Sattler <[EMAIL PROTECTED]> writes:
>> Losses: doesn't work well with many indenting styles (e.g. it would be a
>> complete lose for stuff indented in GNU style).
>
> Can you explain that?
>
> Either the '{' and '}' are one indentation level down or the same indentation
> level.
Because t
Hi Miles!
You wrote:
> Hendrik Sattler <[EMAIL PROTECTED]> writes:
> > represented by tabs and alignment (like multi-line function arguments)
> > should
> > be done by spaces.
> > Gains: shows fine in _every_ editor, no need to set tab-width.
>
> Losses: doesn't work well with many indenting st
Am Montag, 6. März 2006 08:05 schrieb Miles Bader:
> Hendrik Sattler <[EMAIL PROTECTED]> writes:
> > represented by tabs and alignment (like multi-line function arguments)
> > should be done by spaces.
> > Gains: shows fine in _every_ editor, no need to set tab-width.
>
> Losses: doesn't work well
Hendrik Sattler <[EMAIL PROTECTED]> writes:
> represented by tabs and alignment (like multi-line function arguments) should
> be done by spaces.
> Gains: shows fine in _every_ editor, no need to set tab-width.
Losses: doesn't work well with many indenting styles (e.g. it would be a
complete lose f
Am Montag, 6. März 2006 01:28 schrieb Miriam Ruiz:
> bcpp indents C/C++ source programs, replacing tabs with spaces or the
> reverse.
Yet another program that does this wrong? Indentation levels should be
represented by tabs and alignment (like multi-line function arguments) should
be done by s
Package: wnpp
Severity: wishlist
Owner: Miriam Ruiz <[EMAIL PROTECTED]>
* Package name: bcpp
Version : 0.0.20050725
Upstream Author : Steven De Toni <[EMAIL PROTECTED]>
* URL : http://www.invisible-island.net/bcpp/
* License : BSD
Description : C(++) beau
10 matches
Mail list logo
