#1271: Ability to spawn Parrot processes from PIR in tests
-------------------------+--------------------------------------------------
Reporter: whiteknight | Owner: dukeleto
Type: RFC | Status: new
Priority: normal | Milestone:
Component: testing | Version: 1.7.0
Severity: medium | Keywords: test op spawnw
Lang: | Patch:
Platform: all |
-------------------------+--------------------------------------------------
Comment(by cotto):
r42521 will likely be helpful in this task. I went the route of modifying
FileHandle to keep track of the exit status of any children run in a pipe.
I don't know if this is preferable to having spawnw keep track of the exit
code. I just picked the one that seemed easier at the time.
Either way, the code is in place and any stupid API decisions on my part
can be modified since there hasn't been a "supported" release containing
the change.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/1271#comment:4>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
