This may be a matter more of opinion, but does anybody know if there is
a generally accepted length to how long a single line of code should be
before breaking it to the next line with a " _ "? What do you all do?

No, It's up to you.
Most of us just break the line so that it remains visible within the
viewable window.
Sometimes, if I have a particularly long set of arguments to a function I
just let it go on one line; if I want to see all the arguments, I just scroll
over.

But overall, NO there is no standard.
Whatever seems comfortable.

I like to have each argument on separate lines, and the same with the call.
I also prefer to name the parameters in the call.

--
HTH

Bob Phillips

(replace somewhere in email address with gmail if mailing direct)

"FourBlades" wrote in message
...
No, It's up to you.
Most of us just break the line so that it remains visible within the
viewable window.
Sometimes, if I have a particularly long set of arguments to a function I
just let it go on one line; if I want to see all the arguments, I just
scroll
over.

But overall, NO there is no standard.
Whatever seems comfortable.

I like to keep it below 76 characters, that way I don't get it wrapping
around if I print in portrait mode.

I think the NGs does wrap-around at about 72 chars though which is a pain.

--
HTH

Bob Phillips

(replace somewhere in email address with gmail if mailing direct)

"Abe" wrote in message
oups.com...
This may be a matter more of opinion, but does anybody know if there is
a generally accepted length to how long a single line of code should be
before breaking it to the next line with a " _ "? What do you all do?