Don't print warnings at the compilation-time.

Downloaded from https://openclipart.org/detail/234997/push-back-time

Also adding extra eval-when around generic get-cons makes the package
compile under XCL.

Fix proposed by Cliff Brunk:

"I use your Common Lisp metering system pretty often on under MCL 2.01.
Thanks for making this nice profiling tool available, it has helped alot.
However, I notied that the amount of space used by functions that contain
an &optional is much higher for the monitoring-encapsulation than
from the original function.  I beleive this is because the encapsulation
creates a list for the optional arguments using &rest.  If one adds
a dynmaic-extentent declaration after the lambda list in many implementations
of Common Lisp the &rest arglist will be stack allocated and the amount of
storage reported will be a truer indication of how the function performs
outside of the encapsulation.  Below is the modification that I'm currently
using and seems to work at least under MCL.

Cliff Brunk"

Implementation requires compilation (uses C-inlined code), so this
wrapped various things in eval-when to make them work.

If code is only interpreted, ECL will have generic function (like other
implementations which doesn't provide get-cons).

We had no other implementation anyway

This will work only for symbols. Appropriate warning attached.

fdefinition is part of the ANSI standard and deprecates symbol-function

Now it's the default and these conditionals were breaking it. Remove
obsolete code.

Left some still up-to-date allegro code and provided Clozure CL
support (it was the same as the _main_ MCL target).

http://www.cs.cmu.edu/afs/cs/project/ai-repository/ai/lang/lisp/code/tools/metering/