🚀 go-pugleaf

I have heard much about the skills of a *real* hacker but am frustrated
in my attempts to gain these skills.  At present one of my main obstacles
is to reform gcc so as to be more friendly toward *real* hackers. In
particular,
I dream of a gcc filter that will take source directly from stdin, link
it in
memory without creating any temporary files, output to stdout whence
the
executable can be piped straight to the loader and executed.

% gcc | loader
main(){for(;;) fork();} /* :-) */
^D
[ no prompt ]

Who needs the source anyway, once you have the executable?
And after one run, who needs the executable anymore?

Just to make this officially folklore, I should mention that I once
heard
of a great hacker, nay wizard, who typed in the entire Unix OS into such
a
compiler (from memory, of course).  The machine code portions he typed
in straight binary.  And lo! It compiled, and ran flawlessly for 3 hrs
and 12 minutes and some quantum-mechanically indeterminate number of
seconds before giving up the ghost.

There was no evidence of its passing, save some empty diet Coke cans.


						Henri

------------------------------------------------------------------------
----------
Oscar Wilde:  Learning to love oneself is the beginning of a lifelong
romance.
------------------------------------------------------------------------
----------