#379: Generate POSIX errno Constants
-----------------------+----------------------------------------------------
Reporter: chromatic | Owner: whiteknight
Type: RFC | Status: new
Priority: normal | Milestone:
Component: configure | Version:
Severity: medium | Keywords:
Lang: | Patch:
Platform: all |
-----------------------+----------------------------------------------------
Changes (by whiteknight):
* owner: => whiteknight
* type: feature => RFC
Comment:
A better question, I think, is whether we want the err family of opcodes
in Parrot, and whether or not we should be insulating our users from those
kinds of details. I suggest instead that we deprecate the err opcodes, and
not be passing errno values to PIR users. When something goes wrong,
Parrot can take those errno conditions and turn them into exceptions with
the error message and maybe even the errno value included.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/379#comment:3>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
