Re: Poll: Line continuation

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Ken Halter (Ken_Halter_at_Use_Sparingly_Hotmail.com)
Date: 03/08/04 

Date: Mon, 8 Mar 2004 09:22:08 -0800

This API Viewer will format the declarations for you... Single or Multiple lines.

ApiViewer 2003
http://www.activevb.de/rubriken/apiviewer/index-apiviewereng.html 

-- 
Ken Halter - MS-MVP-VB - http://www.vbsight.com
Please keep it in the groups..
"Stefan Berglund" <keepit@in.thegroups> wrote in message
news:9blk40pnqg0m8gdr46lpcrn54im9vac2vp@4ax.com...
> On Sat, 6 Mar 2004 17:25:59 -0500, "Rick Rothstein"
> <rickNOSPAMnews@NOSPAMcomcast.net> wrote:
>  in <#q8$Ao8AEHA.1212@TK2MSFTNGP12.phx.gbl>
>
> >You bring up an interesting point about the usage of line continuations. I
> >posted that I like the ampersand at the end of the line. The reason... I
> >never let a line get longer that the right side of the code window before I
> >continue it; that way, the entire statement is always visible and easy to
> >read. There is no way I would let a statement line get anywhere near 1023
> >characters in length.
> >
> >Rick - MVP
> >
>
> That was in the days before stored procedures.  Now that I no
> longer have any SQL statements in my apps, I don't find any lines
> approaching that length either.  My brain understands code better
> when seen in the context of the surrounding code, and
> continuation lines tend to break up that continuity for me.
>
> I'd also go so far as to say that I don't think anyone should
> attempt to standardize this as I think it's very much a personal
> style thing.  I do like to break up my API declarations however,
> so that every aspect of the declare occupies its own line.

Relevant Pages