begin quoting David Brown as of Wed, Jan 02, 2008 at 03:10:14PM -0800:
> On Wed, Jan 02, 2008 at 02:58:42PM -0800, SJS wrote:
>
> >One of the fancy editors we used when I was using C++ would do that for
> >C++ -- significant closing braces were annotated with what they closed.
> >It was all editor magic, but it was useful as well.
> >
> >I'm suprised that this isn't a feature of some IDE for python yet.
>
> This might be that mindset thing, again.
I think you're correct.
> I find comments:
>
> ...
> } /* if */
>
> to be extremely annoying, to the point of making the code harder to read.
Yah, too many spaces. It needs to be
...
}/*if*/
obviouosly. ;-P
> That close brace is a small turd at the end of a block that the compiler
> needs because it doesn't have any other way to know when the block ends. I
Nah, I need it too.
Or begin .. end works. As does $keyword .. $drowyek.*
> would be perfectly happy if the editor made it a faint gray that was barely
> visible.
You can do that. I typically make my comments a dark blue (on a black
background), as well as anything that starts in column 0 that isn't
"package", "import", or "public".
> Maybe this comes from doing lisp/scheme, where the close parens are almost
> always just placed at the end of the last line. I have seen C code like
> that, but it was fairly unpleasant to read.
I think I annoyed my professor when I we covered scheme, I lined up the
closing parens with the opening parens, as that just made more sense.
Different strokes and all that.
[*] This was the style of the psuedocode that I learned best.
--
If you want universal coding standards, applied to all
Then they should be mine, and all others should fall!
Stewart Stremler
--
KPLUG-LPSG@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
