FASLOAD doesn't respect LDFLG

[rmkaplan]

This became apparent in a recent meeting: (LOAD 'XXX.DFASL) and (LOAD 'XXX.DFASL 'PROP) are equivalent: they both store the new compiled definition in the function cell.

FASL:PROCESS-STREAM doesn't take LDFLG as an argument. Indeed, there is a comment in the code that says that it binds flags internally so that DFASL files are essentially loaded SYSLOAD.

Seems like a bug.

For one thing, it means that GITFNS can't use CALLSCODE to compare the signature of compiled functions, as @masinter suggested. The comparison would smash the current environment.