Eliminate use of temporary files in COMPILE-FILE

[ehuelsmann]

The functions COMPILE and COMPILE-FILE use temporary files for the class files generated by the compiler.

However, COMPILE directly loads them back into memory and deletes the temp file, while COMPILE-FILE deletes the temp file after adding it to a ZIP archive.

This ticket exists to indicate that infrastructure is required to better manage where output goes to, abstracting from the temp files.

[trittweiler]

When working on this, I think it makes sense to base COMPILE-FILE
on a COMPILE-FROM-STREAM. The latter function could then find use
in ABCL's SWANK backend (for implementing C-c C-c.) ECL, and CMUCL
both provide such a COMPILE-FROM-STREAM function.

[ehuelsmann]

Changing ticket title: temp files are no longer used with COMPILE; only with COMPILE-FILE now.

[ehuelsmann]

An intermediate step could be to store the temp files in the location indicated by java.io.tmpdir property. This property should point to a location on local disk, eliminating any network turn-arounds required to stat(), read and delete the files during compilation.

That should at least speed up compilation by a lot in case the target is non-locally stored.

[ehuelsmann]

The suggestion in the previous comment should be doable relatively short term.

[Mark Evenson]

I think has been addressed by Alessio long ago.

[astalla]

I don't recall ever fixing it, and Erik confirms COMPILE-FILE is still using temporary files.