Re: load and use a ".o" file?

[lifetime n00b <anonymous@yahoo.com>]

Jon S. Anthony wrote:

> In CL you don't need an explaination of the mechanism unless you are
> _implementing_ a Common Lisp.  For the user, you don't need to do
> anything other than (compile-file ...) (load ...) to get all the
> resources in native compiled form "linked" in and ready to use.  Or
> for interactive work, just (compile 'your-foo-here).  That's it.  A
> pleasent thing indeed.

See, I just *knew* this was going to turn out more difficult than it 
sounded! :-) First let me say I am not trying to build a complete 
"Common Lisp" implementation, at least not yet. Common Lisp is similar 
to Ada in that both language definitions are very rich and include many 
"libraries" as part of the definition itself that other languages have 
to add on as third party packages. However, one of the nicest features 
of Lisp is that the fundamental syntax of the language is extremely 
elegant and simple.

Right now, it's just this elegant and simple core that I am trying to 
implement, using gnat as the machine-code compiler. It's like a Siren, 
calling me into the deep waters. "Look how beautiful I am! Of course you 
can obtain me, just come a little closer..."

Once I have this core actually working, maybe then I can begin to think 
in terms of adding the myriad functions and operators that make up the 
rest of the Common Lisp definition. And I realize that (compile ...) and 
(load ...) are not part of the core syntax but rather part of the 
"extras" that make up a complete Common Lisp. However, without these, 
there is not much point in continuing on, since the whole point of using 
gnat as the compiler is in the context of these functions.