This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients gvanrossum, larry, ncoghlan, pitrou, skrah
Date 2014-01-06.20:56:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1389041781.43.0.417907208537.issue19723@psf.upfronthosting.co.za>
In-reply-to
Content
I grepped for clinic in the source code and I have a hunch why this confusing: each clinic-generated block has *three* marker comments, each containing [clinic] or [clinic checksum: ...].

TBH I can't always tell on which side of the comment the generated code sits, so I agree it would be nice if there was an additional keyword clearly indicating begin/end.

Looking more carefully it seems the pattern is

/*[clinic]
.
. (this seems to be the clinic input)
.
[clinic]*/
.
. (this seems to be generated)
.
/*[clinic checksum: da39a3ee5e6b4b0d3255bfef95601890afd80709]*/

I expect things would be clearer to the uninitiated if instead they said something like:

/*[clinic input]
.
.
.
[clinic start generated code]*/
.
.
.
/*[clinic end generated code; checksum: da39a3ee5e6b4b0d3255bfef95601890afd80709]*/

Larry, would that be easy?
History
Date User Action Args
2014-01-06 20:56:21gvanrossumsetrecipients: + gvanrossum, ncoghlan, pitrou, larry, skrah
2014-01-06 20:56:21gvanrossumsetmessageid: <1389041781.43.0.417907208537.issue19723@psf.upfronthosting.co.za>
2014-01-06 20:56:21gvanrossumlinkissue19723 messages
2014-01-06 20:56:21gvanrossumcreate