How do you think about the flooding of bracket?
BCS
BCS at pathlink.com
Thu Jun 15 10:06:37 PDT 2006
This looks like a good place for a code scanning tool. It would scan
code and at each "}" find what the matching "{" is coming from and if
their is already a label verify that it is correct, otherwise insert a
label. Might help catch incorrectly matched braces which is what I'm
guessing the "END label" construct is trying to do.
Chris Nicholson-Sauls wrote:
> Deewiant wrote:
>
>> In my mind, when things start to get unreadable due to them spanning
>> many lines
>> and/or there being a lot of nesting, you can just use a comment at the
>> ending
>> curly bracket:
>>
>> void foo() {
>> ...
>> } // end foo()
>
>
> This is generally what I do, except I don't say "end" because I already
> know that -- why else would I document a closing brace? ;) Instead I
> generally put a reminder of the type of the 'foo' I'm ending: function,
> or class, or struct, or whatever. So in the case above, I'd write `//
> function foo`.
>
> -- Chris Nicholson-Sauls
More information about the Digitalmars-d
mailing list