John H Palmieri wrote:
> Ticket #6439 suggests that if code has
>
> Sage: ...
>
> in an EXAMPLES block, then it should be flagged as an error, because
> presumably the author intended it to say
>
> sage: ...
>
> and with "Sage: ..." the example isn't actually doctested. I vote
> against this change: I don't see a reason why we should try to detect
> this typo more than anything else. (Or if we want to make this
> change, should we also flag "sgae:", for instance?) Note that with
> "sage -t -verbose ..." you can see exactly which tests are being run.
> Referees should also be on the lookout for any typos, including ones
> like this. So I would like the ticket to be closed without fixing it,
> but I think this deserves some discussion.
>
> Votes for closing without fixing?
>
Or we might do something like:
if the lowercased characters before a single colon comprise between 3
and 4 of the letters in "sage", and it's not "sage: ", then flag a
possible error.
Or something like a regexp like the following:
^[ ]*[SAGEsage]{3,5}:
I'm all for making people's jobs easier by automating things and
catching typos, even if we don't catch everything.
Jason
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
