Audrey (>):
Indeed... Though what I'm wondering is, is there a hidden implementation
cost or design cost of making /<foo>+/ always behave such that
returns something, compared to the current treatment with the workaround
you suggested?

Has this been settled or addressed off-list? Because from my
perspective as one who has never used P6 rules for anything in
particular, but who in the future most likely will, the proposed
semantics seems a lot saner and more useful. It'd be sad to let pass
this opportunity to fix (what from my perspective appears to be) a
shortcoming of the rule semantics.


Reply via email to