[Openmcl-devel] Using OpenMCL as a shell scripting interpreter
gekki_uk at hotmail.com
Mon Mar 29 03:12:28 EST 2004
I'm not at my mac at the moment, but doesn't the openmcl shell script setup
some environment variables? Have you tried setting these manually in your
shell and then invoking a script.
Probably a red herring, but worth trying.
>From: Gary King <gwking at cs.umass.edu>
>Reply-To: gwking at cs.umass.edu
>To: Stonewall Ballard <sb.list at sb.org>
>CC: OpenMCL <openmcl-devel at clozure.com>
>Subject: Re: [Openmcl-devel] Using OpenMCL as a shell scripting interpreter
>Date: Sun, 28 Mar 2004 21:22:11 -0500
>This is almost completely speculation on my part, but I think that the
>problem might be related to /usr/local/bin/openmcl being a shell script
>itself. I tried messing with scripts calling scripts and found the behavior
>strange (or maybe my test example were...). I tried a script like:
>#! /usr/local/bin/ccl/ccl/dppccl -V
>#! /usr/local/bin/ccl/ccl/dppccl --image-name
>but both of these give the following error: "Couldn't load lisp heap image
>from dppccl.image" (even though they work from the shell prompt).
>So no light shed here but maybe some more smoke...
>On Mar 28, 2004, at 5:53 PM, Stonewall Ballard wrote:
>>I haven't had much time to work on this, so I'd appreciate any help I can
>>Aside from replicating some of my Python utility scripts in Lisp to see
>>whether I feel comfortable with using it that way, my other problem is how
>>to coerce openmcl to run from a simple text file. I'm not going to make a
>>megabyte image for every script - I need to keep them as text until
>>they're run, just like other shell languages.
>>I've tried invoking openmcl with a #! first line in a file, and while
>>openmcl apparently runs, it doesn't go anywhere. I would have thought
>>would print the version number, but I can't find the output anywhere. This
>>works with Python, so I assume that I just need to spend time
>>understanding how openmcl starts up. The code that handles the -V argument
>>just does this (in process-application-arguments):
>> (format t "~&~a~&" (application-version-string a))
>> (force-output t)
>> (#_exit 0))
>>If I can't get this to show up on the terminal, it's going to be rather
>>hard to debug.
>>The next task is to get openmcl to load stdin.
>> - Stoney
>>On Mar 27, 2004, at 4:31 PM, Gary King wrote:
>>>By the way, I'm also interested in a tool of this sort so if you want a
>>>hand, I'd be happy to try and contribute...
>>>On Mar 26, 2004, at 11:25 PM, Stonewall Ballard wrote:
>>>>Very interesting. I hadn't see this before. Thanks for the pointer.
>>>> - Stoney
>>>>On Mar 26, 2004, at 7:40 PM, Gary King wrote:
>>>>>You're probably aware of Olin Shivers work with the Scheme shell, but
>>>>>just in case you're not,
>>>>>http://citeseer.ist.psu.edu/shivers94scheme.html is a good
>>>>>introduction. I really like the idea of a nice Lisp shell built around
>>Openmcl-devel mailing list
>>Openmcl-devel at clozure.com
>Gary Warren King, Lab Manager
>EKSL East, University of Massachusetts * 413 577 0176
>Everyone has the right to life, liberty and security of person.
> -- Universal Declaration of Human Rights, Article 3
>Openmcl-devel mailing list
>Openmcl-devel at clozure.com
It's fast, it's easy and it's free. Get MSN Messenger today!
More information about the Openmcl-devel