PEP scepticism

phil hunt philh at
Sat Jun 30 07:13:02 EDT 2001

On Sat, 30 Jun 2001 01:09:03 GMT, Rainer Deyke <root at> wrote:
>"phil hunt" <philh at> wrote in message
>news:slrn9jq3rc.qg9.philh at
>> On Fri, 29 Jun 2001 17:43:34 -0400, Tim Peters < at> 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.

## Philip Hunt ## philh at ##

More information about the Python-list mailing list