Skip to Content.
Sympa Menu

freetds - Re: indent(1) bent

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: Frediano Ziglio <freddyz77 AT tin.it>
  • To: TDS Development Group <freetds AT franklin.oit.unc.edu>
  • Subject: Re: indent(1) bent
  • Date: 24 Oct 2002 20:52:39 +0200


>
> I don't think the above would be improved by setting tabs to 8, and I don't
> think they would be harmed by setting them to 4, or even harmed much by
> setting them to 5. :)
>

Something raised yesterday in a test.
We spoke about possibility to set tabstop to whatever we want.
But using indentation on parameter lead in a problem

This at code like

variable = myfunction(param1, param2,
param3);

aligned will become something like

\tvariable = myfunction(param1, param2,
\t\t\t\t\t param3);

Using tabspace 8

variable = myfunction(param1, param2,
param3);


unaligned...

Is this a problem?

> > > The nice thing about tabs is that, as long as they're used
> > *consistently*
> > ^^^^^^^^^^^^^^
> > In my experience it just isn't possible to herd cats. It's
> > *impossible*
> > to get a group to use non-8-wide tabs consistently.
> >
> > > and *well* (tab to indent code blocks, spaces if things need to be
> > > indented to line up /within/ a code block), they can
> > satisfy everyone
>
> I respect that. I'm hoping we're different.
>

This is why we are deciding the style for all.

>
> > Personally I like the Linux coding standards, especially for its
> rationales.
>
> I think they're OK, in the Hippocratic sense: they won't hurt. OTOH, some
> of the rationale is a bit antique, don't you think? That we should define
> goodness of function size in terms of "ANSI" screens of 80x24? Please.
> Those days are gone and good riddance. There was *never* a fundamental
> human factors reason for that dimension; it was a function of the state of
> the art of CRT technology, nothing more, nothing less.
>

personally I like to limit sources to 80 column, so I can print with
default characters.

>
> > Anyway, as more editor-flamewar-fuel, I think vim is best for
> > hopping around
> > between coding styles. sw, ts and et can all be controlled
> > separately. Try doing that with "Other OS" IDE editors. :)
>
> I keep telling myself I should learn emacs, and keep hoping nedit will grow
> all the features I want, so I won't have to.
>

I'm using vim and Anjuta (I think based on scintilla)...
Anyone know some quick manual for C/C++ programmer to emacs? Some
prepared simple configurations?

freddy77






Archive powered by MHonArc 2.6.24.

Top of Page