Audacity and pipe_test.py

[Steve]

" The problem is that since they're comments, the compiler can't warn you
when there's a mistake.  After the code has been edited a few times, they
will end up being wrong and misleading."

If that is the case, then I would suspect that you are doing it incorrectly.
It works especially well for me.  It goes a long way to help with indents.
It also prevents a lot of excessive scrolling.

I do something similar with HTML.  A comment at the end of a data structure
that explains the purpose of the DS is extremely helpful.





-----Original Message-----
From: Python-list <python-list-bounces+gronicus=sga.ninja at python.org> On
Behalf Of Grant Edwards
Sent: Sunday, September 13, 2020 9:41 PM
To: python-list at python.org
Subject: Re: Audacity and pipe_test.py

On 2020-09-13, Steve <Gronicus at SGA.Ninja> wrote:
> "There is no promise on time.sleep() that the program will restart 
> exactly when the time expires."
>
> No precision needed, +- two minutes is acceptable, even three..  In my 
> tests, I see scarcely three seconds difference.  No problem.
>
> As for ENDIF, ENDWHILE,
> "But they have no syntactic meaning, and may get out of sync with the 
> indentation."
>
> Being comments, will have no effect of indents.

Exactly. That's the problem.

> I use them strictly to see the structure and usually for long segments 
> of code only.

The problem is that since they're comments, the compiler can't warn you when
there's a mistake.  After the code has been edited a few times, they will
end up being wrong and misleading.

If you can't see the structure of the code by looking at the code, then
you're doing something wrong.  Fix the code (or use a better editor). Adding
comments to try to clarify the flow of poorly structured code just ends up
making the problem worse later on when the comments are wrong.  And they
will end up being wrong.








--
https://mail.python.org/mailman/listinfo/python-list