#1298: opcodes, warnings, and exceptions
----------------------+-----------------------------------------------------
Reporter: particle | Owner:
Type: RFC | Status: new
Priority: trivial | Milestone:
Component: none | Version:
Severity: medium | Keywords:
Lang: | Patch:
Platform: |
----------------------+-----------------------------------------------------
the api for opcodes needs review, especially with regard to the
response to exceptional behavior. for example, the documentation for
B<length> in src/ops/string.ops reads:
{{{
=item B<length>(out INT, in STR)
Set result $1 to the length (in characters) of string $2.
If $2 is NULL or zero length, zero is returned.
}}}
however, if a null string is passed in to length, the user should get
some notification of an exceptional condition. *at least* a warning,
and possibly a fatal exception.
~jerry
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1298>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
