Update of /project/lispfaq/cvsroot/lispfaq In directory common-lisp.net:/tmp/cvs-serv24224

Modified Files: faq.css faq.xsl freelisp.xml hello-world.xml no-data-types.xml on-topic.xml online.xml prolisp.xml scheme.xml Log Message:

- formatting changes: updated style-sheet, first section now on separate chunk

- fixed links to old HyperSpec location

Date: Tue Mar 23 05:11:47 2004 Author: emarsden

Index: lispfaq/faq.css diff -u lispfaq/faq.css:1.1.1.1 lispfaq/faq.css:1.2 --- lispfaq/faq.css:1.1.1.1 Fri Mar 5 13:17:14 2004 +++ lispfaq/faq.css Tue Mar 23 05:11:47 2004 @@ -1,121 +1,85 @@ -SPAN.EMPHASIS, SPAN.ULINK1, SPAN.TITLE1, SPAN.ARTICLE { - font-family: Times New Roman; - font-weight: 500; - font-style: italic; - font-size: 10pt; - color: #000000; -} -SPAN.ULINK2, SPAN.TITLE3 { - font-family: Times New Roman; - font-weight: 700; - font-style: normal; - font-size: 24.883pt; - color: #000000; -} -SPAN.FUNCTION, SPAN.COMPUTEROUTPUT { - font-family: Courier New; - font-weight: 500; - font-style: normal; - font-size: 9pt; - color: #000000; -} -SPAN.USERINPUT { - font-family: Courier New; - font-weight: 700; - font-style: normal; - font-size: 10pt; - color: #000000; -} -SPAN.LITERALLAYOUT, SPAN.TERM2, SPAN.LISTITEM2, SPAN.ANSWER2, SPAN.QUESTION3, SPAN.ULINK3, SPAN.PARA2 { - font-family: Times New Roman; - font-weight: 500; - font-style: normal; - font-size: 10pt; - color: #000000; -} -SPAN.COMMAND, SPAN.QUESTION2, SPAN.TITLE5 { - font-family: Times New Roman; - font-weight: 700; - font-style: normal; - font-size: 10pt; - color: #000000; -} -DIV { margin-top: 0pt; margin-bottom: 0pt; margin-left: 0pt; margin-right: 0pt } -DIV.TITLE7 { - margin-top: 2.5pt; - text-align: left; - line-height: 13pt; - text-indent: 0pt; -} -DIV.LISTITEM3 { - margin-left: 20pt; - margin-top: 5pt; - text-align: left; - line-height: 13pt; - text-indent: -20pt; -} -DIV.LITERALLAYOUT, DIV.TERM3 { - margin-top: 10pt; - text-align: left; - line-height: 13pt; - text-indent: 0pt; -} -DIV.LISTITEM1 { - margin-left: 44pt; - margin-top: 5pt; - text-align: left; - line-height: 13pt; - text-indent: -20pt; -} -DIV.PARA5, DIV.TERM1, DIV.QUESTION1 { - margin-left: 24pt; - margin-top: 10pt; - text-align: left; - line-height: 13pt; - text-indent: 0pt; -} -DIV.TITLE4, DIV.PARA3 { - margin-top: 5pt; - text-align: left; - line-height: 13pt; - text-indent: 0pt; -} -DIV.QUESTION6, DIV.ANSWER1 { - margin-left: 24pt; - margin-top: 2.5pt; - text-align: left; - line-height: 13pt; - text-indent: 0pt; -} -DIV.ANSWER4, DIV.QUESTION4 { - margin-left: 24pt; - text-align: left; - line-height: 13pt; - text-indent: 0pt; -} -DIV.ANSWER3, DIV.QUESTION5, DIV.PARA4 { - margin-left: 24pt; - margin-top: 5pt; - text-align: left; - line-height: 13pt; - text-indent: 0pt; -} -DIV.TITLE6 { - text-align: left; - line-height: 13pt; - text-indent: 0pt; -} -DIV.PARA1 { - margin-left: 18.803pt; - margin-right: 18.803pt; - margin-top: 5pt; - text-align: left; - line-height: 13pt; - text-indent: 0pt; -} -DIV.TITLE2 { - margin-top: 18.662pt; - text-align: center; - line-height: 32.348pt; - text-indent: 0pt; +html { + color: black; + background-color: white; + margin-left: 4%; + margin-right: 2%; +} + +h1 { + text-align: center; + font-family: Helvetica, Arial, sans-serif +} + +h2 { + color: #515e4b; + font-family: Helvetica, Arial, sans-serif +} + +h3 { + font-family: Helvetica, Arial, sans-serif; +} + +.lisp { + background: #aaaaaa; + border:solid #aaaaaa 0.1px; + white-space:pre; + font-family: sans-serif; +} + +.example { + background: #cccccc; + border:solid #cccccc 0.1px; + white-space:pre; +} + +.code { + background: #faf0e6; + border:solid #faf0e6 1px; + white-space:pre; +} + +.technical { + background: #dddddd; + border: solid black 1px; + padding-left: 1em; + padding-right: 1em; + padding-top: 1ex; + padding-bottom: 1ex; + font-size: smaller; + font-stretch: semi-condensed; + margin-left: 10%; +} + +.credits { + background: #eeeeee; + font-stretch: condensed; + font-size: 0.8em; + font-family: Helvetica, Arial, sans-serif; + text-align: right; +} + +.function-name { + color: rgb(25%,0%,0%); +} + +.variable { + color: rgb(0%,25%,0%); +} + + +A:link +{ + text-decoration: none +} +A:active +{ + text-decoration: none +} +A:visited +{ + text-decoration: none +} +A:hover +{ + text-decoration: underline }

Index: lispfaq/faq.xsl diff -u lispfaq/faq.xsl:1.2 lispfaq/faq.xsl:1.3 --- lispfaq/faq.xsl:1.2 Mon Mar 22 15:07:41 2004 +++ lispfaq/faq.xsl Tue Mar 23 05:11:47 2004 @@ -6,7 +6,7 @@

<xsl:import href="xhtml/chunk.xsl"/>

- <xsl:param name="html.stylesheet" select="'lispfaq.css'"/> + <xsl:param name="html.stylesheet" select="'faq.css'"/> <xsl:param name="section.autolabel" select="1"/> <xsl:param name="qandadiv.autolabel" select="1"/> <xsl:param name="use.id.as.filename" select="1"/> @@ -14,6 +14,7 @@ <xsl:param name="css.decoration" select="1"/> <xsl:param name="make.valid.html" select="1"/> <xsl:param name="html.extra.head.links" select="1"/> + <xsl:param name="chunk.first.sections" select="1"/> <xsl:param name="chunker.output.encoding" select="'ISO-8859-1'"/>

<xsl:template name="user.head.content">

Index: lispfaq/freelisp.xml diff -u lispfaq/freelisp.xml:1.2 lispfaq/freelisp.xml:1.3 --- lispfaq/freelisp.xml:1.2 Mon Mar 22 15:07:41 2004 +++ lispfaq/freelisp.xml Tue Mar 23 05:11:47 2004 @@ -52,15 +52,15 @@ </varlistentry> <varlistentry> <term><ulink - url="http://ecls.sourceforge.net/%22%3EECLS</ulink></term> + url="http://ecls.sourceforge.net/%22%3EECL</ulink></term> <listitem> <para> - Standing for `Embeddable Common Lisp', ECL is an - implementation of Common Lisp running on at least x86, - Sparc and PPC architectures, under Linux, FreeBSD, - Solaris, MacOSX and Windows (Using the CYGWIN - environment). As well as a bytecode compiler, ECL can - compile to C. ECL is licensed under the GNU LGPL. + Standing for <productname>Embeddable Common + Lisp</productname>, ECL is an implementation of Common + Lisp running on at least x86, Sparc and PPC architectures, + under Linux, FreeBSD, Solaris, MacOSX and Windows (using + the cygwin environment). As well as a bytecode compiler, + ECL can compile to C. ECL is licensed under the GNU LGPL. </para> </listitem> </varlistentry> @@ -69,12 +69,13 @@ url="http://savannah.gnu.org/projects/gcl/%22%3EGCL</ulink></term> <listitem> <para> - Gnu Common Lisp has languished in the past as a non-ANSI - compliant Common Lisp; recent times have let it see more - developments towards supporting the ANSI Common Lisp - standard. It cannot (yet) be recommended as a Common Lisp, - but it is still useful for running software written for it - (primarily Maxima). GCL is licensed under the GNU LGPL. + <productname>GNU Common Lisp</productname> has languished + in the past as a non-ANSI compliant Common Lisp; recent + times have let it see more developments towards supporting + the ANSI Common Lisp standard. It cannot (yet) be + recommended as a Common Lisp, but it is still useful for + running software written for it (primarily Maxima). GCL is + licensed under the GNU LGPL. </para> </listitem> </varlistentry> @@ -83,10 +84,11 @@ url="http://openmcl.clozure.com/%22%3EOpenMCL</ulink></term> <listitem> <para> - OpenMCL is an `opensourced' version of a port of a subset - of MCL 4.2, and runs on powerpc/Linux. Not quite all - functionality is yet present, but it is improving - rapidly. OpenMCL is licensed under the GNU LGPL + OpenMCL is an opensourced Common Lisp implementation + derived from MCL 4.2, and runs on MacOS X and + Linux/PowerPC. It includes a bridge to the Cocoa framework + that allows convenient manipulation of Objective C objects + in CLOS. OpenMCL is licensed under the GNU LGPL. </para> </listitem> </varlistentry> @@ -95,7 +97,11 @@ url="http://www.poplog.org/%22%3EPoplog</ulink></term> <listitem> <para> - Poplog is licensed under an XFree86-style license. + Poplog is an incrementally-compiled runtime that includes + a Common Lisp implementation, an ML implementation and a + Prolog implementation, all cohabiting in the same image. + It is licensed under an XFree86-style license. Poplog CL is + not actively maintained. </para> </listitem> </varlistentry> @@ -106,9 +112,10 @@ <para> SBCL is a fork from CMUCL aimed at improving the maintainability by removing the bootstrapping issues - involved in recompiling. Currently it runs on x86/Linux - and alpha/Linux. SBCL is licensed in a similar fashion to - CMUCL. + involved in recompiling. Currently it runs on x86/Linux, + x86/FreeBSD, PowerPC/Linux, MacOS X, MIPS/Linux, + HPPA/Linux and Alpha/Linux. SBCL is licensed in a similar + fashion to CMUCL. </para> </listitem> </varlistentry>

Index: lispfaq/hello-world.xml diff -u lispfaq/hello-world.xml:1.1 lispfaq/hello-world.xml:1.2 --- lispfaq/hello-world.xml:1.1 Mon Mar 22 13:55:25 2004 +++ lispfaq/hello-world.xml Tue Mar 23 05:11:47 2004 @@ -17,8 +17,10 @@ </para> <para> Something which is closer to the canonical "Hello, World!" - attempt is <userinput>(format t "~&amp;Hello, - World!~%")</userinput>. + attempt is + <userinput> + (write-line "Hello, World!") + </userinput> </para> </answer> </qandaentry>

Index: lispfaq/no-data-types.xml diff -u lispfaq/no-data-types.xml:1.1 lispfaq/no-data-types.xml:1.2 --- lispfaq/no-data-types.xml:1.1 Mon Mar 22 13:55:25 2004 +++ lispfaq/no-data-types.xml Tue Mar 23 05:11:47 2004 @@ -5,13 +5,13 @@ <answer> <para> If arrays and structures don't exist, then obviously <ulink - url="http://www.xanalys.com/software_tools/reference/HyperSpec/Body/f_mk_ar.htm%2...</ulink> + url="http://www.lispworks.com/reference/HyperSpec/Body/f_mk_ar.htm%22%3EMAKE-ARRA...</ulink> and <ulink - url="http://www.xanalys.com/software_tools/reference/HyperSpec/Body/m_defstr.htm%...</ulink> + url="http://www.lispworks.com/reference/HyperSpec/Body/m_defstr.htm%22%3EDEFSTRUC...</ulink> must be figments of the imagination. Similarly, since Lisp only uses association lists to organize "database-like" information, <ulink - url="http://www.xanalys.com/software_tools/reference/HyperSpec/Body/f_mk_has.htm%...</ulink> + url="http://www.lispworks.com/reference/HyperSpec/Body/f_mk_has.htm%22%3EMAKE-HAS...</ulink> must also be a figment of the imagination. </para> <para>

Index: lispfaq/on-topic.xml diff -u lispfaq/on-topic.xml:1.2 lispfaq/on-topic.xml:1.3 --- lispfaq/on-topic.xml:1.2 Mon Mar 22 15:07:41 2004 +++ lispfaq/on-topic.xml Tue Mar 23 05:11:47 2004 @@ -4,7 +4,7 @@ </question> <answer> <para> - Disscussion of the language defined by the ANSI Common Lisp + Discussion of the language defined by the ANSI Common Lisp standard is definitely on-topic on comp.lang.lisp. Unlike comp.lang.c, we do not restrict our discussions to the standard, but also actively discuss the differences between

Index: lispfaq/online.xml diff -u lispfaq/online.xml:1.2 lispfaq/online.xml:1.3 --- lispfaq/online.xml:1.2 Mon Mar 22 15:07:41 2004 +++ lispfaq/online.xml Tue Mar 23 05:11:47 2004 @@ -5,7 +5,7 @@ <answer> <variablelist> <varlistentry> - <term><ulink url="http://www.xanalys.com/software_tools/reference/HyperSpec/Front/index.html">The Common Lisp Hyperspec</ulink></term> + <term><ulink url="http://www.lispworks.com/reference/HyperSpec/Front/">The Common Lisp Hyperspec</ulink></term> <listitem> <para>A non-normative transferral of the official ANSI standard for Common Lisp to the hypertext medium, by @@ -25,6 +25,19 @@ <listitem> <para>An on-line Wiki-equivalent with emphasis on Free software written in Common Lisp.</para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="http://planet.lisp.org/">Planet.Lisp</ulink></term> + <listitem> + <para>Aggregator for the weblogs and diaries of various + Common Lisp hackers.</para> + </listitem> + </varlistentry> + <varlistentry> + <term><ulink url="http://common-lisp.net/">Common-Lisp.net</ulink></term> + <listitem> + <para>Home to a number of Common Lisp development projects.</para> </listitem> </varlistentry> </variablelist>

Index: lispfaq/prolisp.xml diff -u lispfaq/prolisp.xml:1.1 lispfaq/prolisp.xml:1.2 --- lispfaq/prolisp.xml:1.1 Mon Mar 22 13:55:25 2004 +++ lispfaq/prolisp.xml Tue Mar 23 05:11:47 2004 @@ -1,6 +1,6 @@ <qandaentry> <question> - <para>Where can I buy a professional lisp system?</para> + <para>Where can I buy a commercial lisp system?</para> </question> <answer> <para>There are a fair few commercial vendors of Lisp systems; the @@ -11,13 +11,13 @@ <listitem> <para>Franz Inc's Allegro Common Lisp is a fine lisp development environment. See their website for more - details</para> + details.</para> </listitem></varlistentry> <varlistentry> <term><ulink url="http://www.xanalys.com/">LCL</ulink></term> <listitem> <para>LCL (formerly Liquid Common Lisp) is an offering from - Xanalys</para> + Xanalys.</para> </listitem></varlistentry> <varlistentry> <term><ulink @@ -25,7 +25,7 @@ <listitem> <para>Another offering from Xanalys, LispWorks has a different set of extensions above the ANSI specification - from LCL</para> + from LCL.</para> </listitem></varlistentry> <varlistentry> <term><ulink

Index: lispfaq/scheme.xml diff -u lispfaq/scheme.xml:1.1 lispfaq/scheme.xml:1.2 --- lispfaq/scheme.xml:1.1 Mon Mar 22 13:55:25 2004 +++ lispfaq/scheme.xml Tue Mar 23 05:11:47 2004 @@ -6,9 +6,10 @@ <para> Scheme is a member of the greater family of Lisp languages, assuming that is considered to include others like Dylan and - Emacs Lisp. The design of Scheme predates the ANSI Common Lisp - standard, and some CL features such as lexical scoping may be - considered to have been derived from Scheme. + Emacs Lisp. The design of Scheme <emphasis>predates</emphasis> + the ANSI Common Lisp standard, and some CL features such as + lexical scoping may be considered to have been derived from + Scheme. </para> <para> More detailed comparative discussions don't generally prove very