Internally, Morloc captures error messages code raises directly and communicates through dedicated sockets. It does not internally use STDOUT or STDERR, but it does use STDOUT as its default pipe for formatted output. To avoid mixing STDOUT created by the program with STDOUT created by Morloc, the generated code will capture and eat all internal STDOUT. This may not be desirable if the user actually wants to create non-Morloc STDOUT.

So how should Morloc behave? STDERR is already fine, it passes through Morloc transparently. For STDOUT, we may need to allow the user to set the desired behavior. Here are a few possibilities:

1. Print Morloc formatted data, send internal STDOUT to DEVNULL (the current default)
2. Send Morloc formatted data to DEVNULL, print internal STDOUT
3. Write Morloc formatted data to a dedicated file, print internal STDOUT
4. Write internal STDOUT to a dedicated file, send Morloc formatted output to STDOUT
5. Write both to dedicated files
6. Write everything to STDOUT, damn the consequences
7. Capture STDOUT and write it into the packet metadata block (require voidstar output)
8. Capture STDOUT and STDERR and write both to packet metadata block (require voidstar output)