PEP scepticism

Michael Manti mmanti at home.com
Sun Jul 1 02:56:41 CEST 2001


On Saturday 30 June 2001 07:13, you wrote:
> On Sat, 30 Jun 2001 01:09:03 GMT, Rainer Deyke <root at rainerdeyke.com> wrote:
> >"phil hunt" <philh at comuno.freeserve.co.uk> wrote in message
> >news:slrn9jq3rc.qg9.philh at comuno.freeserve.co.uk...
> >
> >> On Fri, 29 Jun 2001 17:43:34 -0400, Tim Peters <tim.one at home.com> wrote:
> >> >Or the other existing method:
> >> >
> >> >    # This is a multi-line comment.
> >> >    # Although it sure looks like a sequence of
> >> >    # single-line comments <wink>.
> >>
> >> This is truly bad, because it makes it harder to add new lines;
> >> you have to type "# " repeatedly when adding new comment text, which
> >> breaks the flow of thought -- at least it dores for me.
> >
> >Strange.  In C++, I always use '//' for multiline comments in favor of
> >'/**/'.  ('//' in C++ is equivalent to '#' in Python.)  This makes the
> >comment more readable IMO.  Why not just type the comment text first, and
> >add '#' marks later?
>
> That's what I do. I still find it an irritating hassle.
>
> I appreciate your point that beginning all comment lines with //
> makes for visibility. When I have long multi-line comment, I
> usually enclose them like this:
>
> /*********
> Start of long comment
>
>
>
>
>
> end of long comment
> *********/
>
> Which I find nice and visible.

Which editor or IDE do you use that makes commenting such an "irritating 
hassle"? I think just about every programming mode in Emacs has a convenient 
function and keybinding for commenting--the modes for Python and C/C++ 
included--and I'd be genuinely surprised if other editors and IDEs didn't 
have the same.






More information about the Python-list mailing list