[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Axiom-developer] GCC/GCL warning messages
From: |
Gabriel Dos Reis |
Subject: |
Re: [Axiom-developer] GCC/GCL warning messages |
Date: |
Mon, 5 Mar 2007 13:25:18 -0600 (CST) |
On Mon, 5 Mar 2007, Camm Maguire wrote:
| Greetings!
|
| Gabriel Dos Reis <address@hidden> writes:
|
| > On Fri, 2 Mar 2007, Camm Maguire wrote:
| >
| > | [ Note: Back from one month out of office ]
| >
| > Welcome back!
| >
| > Please could you hand hold me a bit through GCL?
| >
| > I'm interested in processing command line arguments used to invoke GCL or
| > images obtained from saving GCL. In particular, assume I have a saved
| > image "foo", and it is invoked like this:
| >
| > ./foo --mumble --jumble=bar
| >
| > How do I get my hand on the command line arguments --mumble and
| > --jumble=bar?
| >
|
| A good example is gcl-top-level, for example:
|
| (si::get-command-arg "-compile")
|
| >
| > Furthermore, is there an equivalent of C's main() function in GCL?
| >
|
| A good idea is to set si::*top-level-hook*, like in hol88:
|
| (progn
| (setq si::*top-level-hook* (lambda nil (tml)))
| (gbc t)
| (si::save-system file))
|
| 'tml is their top level.
Wonderful.
Many thanks, Camm.
-- Gaby