From: Rob Warnock Subject: Re: Help with macro to list structure properties? Date: Message-ID: <nOmdnQZd9uDHdBLfRVn-uA@speakeasy.net>
Jeffrey Cunningham <····················@boeing.com> wrote:
+---------------
| In notice when I fire up CMUCL in python that it says:
| Loaded subsystems:
| Python 1.1, target Intel x86
| CLOS 18e (based on PCL September 16 92 PCL (f))
| *
| What is Python doing in this?
+---------------
<http://www.cons.org/cmucl/FAQ.html>
...
4. Q: Why does CMUCL say it's called Python 1.1 when it starts up?
Isn't that the name of a scripting language?
A: The CMUCL native code compiler is called Python. This use of the
name predates the existence of that other scripting language.
-Rob
-----
Rob Warnock <····@rpw3.org>
627 26th Avenue <URL:http://rpw3.org/>
San Mateo, CA 94403 (650)572-2607From: Kalle Olavi Niemitalo Subject: Python of CMUCL (was: Help with macro to list structure properties?) Date: Message-ID: <87br733dtc.fsf@Astalo.kon.iki.fi>
····@rpw3.org (Rob Warnock) writes: > <http://www.cons.org/cmucl/FAQ.html> > ... > 4. Q: Why does CMUCL say it's called Python 1.1 when it starts up? > Isn't that the name of a scripting language? > > A: The CMUCL native code compiler is called Python. This use of the > name predates the existence of that other scripting language. For a while, I wondered whether the compiler is separate enough to deserve its own name and version number, especially as SBCL has already dropped :PYTHON from *FEATURES*. But CVS shows that C::COMPILER-VERSION has been changed twice: first from "0.0" to "1.0" on 1991-03-12, and then to "1.1" on 2003-02-05.