* Using files, not pipes, to communicate results, to avoid deadlock due to full buffers.
* Major simplification by hooking into recent ASDF's perform-plan interface,
 rather than kludging our way around perform for parallel operations.
* Take advantage of ASDF 2.26.15's new internal traverse and action-stamp APIs.

This is a major rewrite of several subsystems of POIU.
NB: it looks like some race condition it making things hard for us on either SBCL or CCL.
This isn't stable. Try POIU 1.027 with ASDF 2.26 for stable results.

for incremental builds.
Another attempt at fixing to-go counts.

Get undefined-warning reports in the correct branch;
treat SETF function names correctly.

Fix normalize-dependencies to use proper parent namespace for non-flat systems.
Add deferred warning infrastructure by Douglas Katzman (SBCL only for now).

external-format, *compile-op-compile-file-function*, compile-flags).
For that, depend on ASDF 2.21 or later (2.23 or later preferred).
Also, override any with-compilation-unit when compiling in a fork.
If that causes warnings you don't like to be emitted...
use asdf-condition-control.

* have system depend on asdf.
* know how to recover when signals dropped.
* define parallel-load-system, parallel-compile-system.
* make test executable as a shell script.
* I can make clisp break mostly reliably on fare-utils
 if both module pure and stateful depend on base as well as interface(!)
 it then claims "Cycle detected".

instead have the new operations depend on both "internal" component-depends-on
dependencies AND on "external" component-do-first dependencies, both frobbed.

Looks like it's working, now.

Make POIU depend on said ASDF version.

(thanks to Samium Gromoff for the bug report.)

1- Better explain how to use it.
2- Explain why we redefine classes. Sigh.
3- Use :keywords for LOOP keywords.
4- have the test auto-exit.

i.e. you can (asdf:load-system :poiu)
rather than manually doing (load "/path/to/poiu.lisp")