Changeset 8822


Ignore:
Timestamp:
Mar 18, 2008, 8:16:28 PM (11 years ago)
Author:
gz
Message:

Use &CCL; consistently

Location:
trunk/source/doc/src
Files:
5 edited

Legend:

Unmodified
Added
Removed
  • trunk/source/doc/src/ffi.xml

    r8820 r8822  
    19101910    <para>You are likely to see these reader macros used extensively
    19111911      in Lisp code that works with foreign libraries; for example,
    1912       Clozure CL IDE code, which defines numerous Objective-C classes
     1912      &CCL; IDE code, which defines numerous Objective-C classes
    19131913      and methods, uses these reader macros extensively.</para>
    19141914
     
    41444144        <title>Description</title>
    41454145       
    4146         <para>In Clozure CL 1.2 and later, the #&gt; reader macro reads
     4146        <para>In &CCL; 1.2 and later, the #&gt; reader macro reads
    41474147          the following text as a keyword, preserving the case of the
    41484148          text. For example:</para>
  • trunk/source/doc/src/ide.xml

    r8820 r8822  
    1515  <sect1><title>Introduction</title>
    1616   
    17     <para>Clozure CL ships with the complete source code for an integrated
     17    <para>&CCL; ships with the complete source code for an integrated
    1818    development environment written using Cocoa on Mac OS X. This
    1919    chapter describes how to build and use that environment,
     
    3434  <sect1><title>Building the IDE</title>
    3535   
    36     <para>Building the Clozure CL IDE is now a very simple
     36    <para>Building the &CCL; IDE is now a very simple
    3737      process.</para>
    3838
     
    6969    </programlisting>
    7070
    71     <para>Clozure CL compiles and loads the various subsystems that
     71    <para>&CCL; compiles and loads the various subsystems that
    7272      make up the IDE, then constructs a Cocoa application bundle
    7373      named "Clozure CL.app" and saves the Lisp image into
  • trunk/source/doc/src/install.xml

    r8820 r8822  
    201201
    202202      <sect2 id="The-openmcl-Shell-Script"><title>The openmcl Shell Script"</title>
    203       <para>Clozure CL needs to be able to find the
     203      <para>&CCL; needs to be able to find the
    204204      <literal>ccl</literal> directory in order to support features
    205205      such as <literal>require</literal> and
  • trunk/source/doc/src/streams.xml

    r8820 r8822  
    5858    <sect2 id="Open-File-Streams">
    5959      <title>Open File Streams</title>
    60       <para>Historically, Clozure CL and MCL maintained a list of open
     60      <para>Historically, &CCL; and MCL maintained a list of open
    6161      file streams in the value of
    6262      <literal>CCL:*OPEN-FILE-STREAMS*</literal>.  This functionality
  • trunk/source/doc/src/using.xml

    r8820 r8822  
    1616    <para>The Common Lisp standard allows considerable latitude in the
    1717      details of an implementation, and each particular Common Lisp
    18       system has some idiosyncracies. This chapter describes ordinary <code>foo</code>
     18      system has some idiosyncracies. This chapter describes ordinary
    1919      user-level features of &CCL;, including features that may be
    2020      part of the Common Lisp standard, but which may have quirks or
     
    2424  </sect1>
    2525
    26   <sect1 id="m_trace0"><title>Trace</title>
     26  <sect1 id="Trace"><title>Trace</title>
    2727
    2828  <para>
     
    480480  <sect1 id="Unicode"><title>Unicode</title>
    481481
    482   <para>All characters and strings in Clozure CL fully support Unicode
     482  <para>All characters and strings in &CCL; fully support Unicode
    483483  by using UTF-32. There is only one <literal>CHARACTER</literal> type
    484   and one <literal>STRING</literal> in Clozure CL.  There has been a
     484  and one <literal>STRING</literal> in &CCL;.  There has been a
    485485  lot of discussion about this decision which can be found by
    486486  searching the openmcl-devel archives at <ulink
     
    490490
    491491  <sect2><title>Characters</title>
    492   <para>There is one <literal>CHARACTER</literal> type in Clozure CL.
     492  <para>There is one <literal>CHARACTER</literal> type in &CCL;.
    493493  All <literal>CHARACTER</literal>s are <literal>BASE-CHAR</literal>s.
    494494  <varname>CHAR-CODE-LIMIT</varname> is now
     
    503503  value (an undefined/non-standard <literal>CHARACTER</literal>
    504504  object) for other unassigned code values.</para>
    505   <para>Clozure CL supports character names of the form
     505  <para>&CCL; supports character names of the form
    506506  <literal>u+xxxx</literal> - where <literal>x</literal> is a sequence
    507507  of one or more hex digits.  The value of the hex digits denotes the
     
    609609
    610610  <sect2 id="Character-Encodings"><title>Character Encodings</title>
    611   <para>Internally, all characters and strings in Clozure CL are in
     611  <para>Internally, all characters and strings in &CCL; are in
    612612  UTF-32.  Externally, files or socket streams may encode characters
    613613  in a wide variety of ways.  The International Organization for
    614614  Standardization, widely known as ISO defines a number of these
    615   character encodings.  Clozure CL implements a number of these
     615  character encodings.  &CCL; implements a number of these
    616616  encodings as detailed below.  These encodings are part of the
    617617  specification of external formats (see <xref
     
    841841  <sect2 id="Predefined-Logical-Hosts"><title>Predefined Logical Hosts</title>
    842842
    843   <para>Clozure CL sets up logical pathname translations for logical hosts:  <literal>ccl</literal> and <literal>home</literal></para>
     843  <para>&CCL; sets up logical pathname translations for logical hosts:  <literal>ccl</literal> and <literal>home</literal></para>
    844844
    845845  <indexterm><primary>CCL Logical Host</primary></indexterm>
    846846  <para>The <literal>CCL</literal> logical host should point to the
    847847  <literal>ccl</literal> directory.  It is used for a variety of
    848   purposes by Clozure CL including: locating Clozure CL source code,
     848  purposes by &CCL; including: locating &CCL; source code,
    849849  <literal>require</literal> and <literal>provide</literal>, accessing
    850   foreign function information, and the Clozure CL build process. It
     850  foreign function information, and the &CCL; build process. It
    851851  is set to the value of the environment variable
    852852  <varname>CCL_DEFAULT_DIRECTORY</varname>, which is set by the
     
    860860    <title>OS X (Darwin)</title>
    861861   
    862     <para>Clozure CL assumes that pathname strings are decomposed UTF-8.</para>
     862    <para>&CCL; assumes that pathname strings are decomposed UTF-8.</para>
    863863  </sect2>
    864864  <sect2>
Note: See TracChangeset for help on using the changeset viewer.