Ticket #152 (closed RFC: done)
Do we need PARROT_CATCH_NULL?
Reported by: | coke | Owned by: | whiteknight |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | core | Version: | |
Severity: | medium | Keywords: | |
Cc: | petdance | Language: | |
Patch status: | Platform: |
Description
svn blame of PARROT_CATCH_NULL's definition says:
13169 chip /* TODO - Make this a config option */ 4643 leo #define PARROT_CATCH_NULL 1
This behavior is pretty entrenched. Do we still want this to be configurable, or can delete the other option?
Change History
Note: See
TracTickets for help on using
tickets.