#552: Evaluate all hack-identifying comments in source code
---------------------+------------------------------------------------------
Reporter: jkeenan | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: none | Version:
Severity: medium | Keywords: hack gci
Lang: | Patch:
Platform: all |
---------------------+------------------------------------------------------
Changes (by cotto):
* keywords: hack => hack gci
Comment:
I'd like to close this ticket. We do want to have a way to draw attention
to noteworthy comments, so here's what I'd propose: We should find some
enterprising gci student to write a script (perl, PIR or nqp-rx) in
tools/dev to identify all comments, mangle it into trac wiki syntax and
add some links to individual files and lines on github
([https://github.com/parrot/parrot/blob/master/src/embed.c#L62 example]).
Once we have such a script, we can update the wiki with its output as
needed and we can close this ticket.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/552#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
