Author: housel
Date: Sat May 14 20:52:43 2005
New Revision: 9873
Modified:
trunk/documentation/topic/concept/lid-files.xml
Log:
Bug: 7249
Fix links, tighten text.
Modified: trunk/documentation/topic/concept/lid-files.xml
==============================================================================
--- trunk/documentation/topic/concept/lid-files.xml (original)
+++ trunk/documentation/topic/concept/lid-files.xml Sat May 14 20:52:43 2005
@@ -14,22 +14,22 @@
format for Dylan libraries. Without such an agreed format,
different Dylan development environments would find it difficult
to import and build libraries developed using another Dylan
- vendor’s environment. It would also be impossible to automate the
+ environment. It would also be impossible to automate the
process of importing a library into another environment.</p>
- <p>LID solves this problem. It allows you to describe Dylan
- library sources in a form that any Dylan environment should be
- able to understand. Dylan vendors have adopted LID to make it
+ <p>LID solves this problem. It allows programmers to describe
+ Dylan library sources in a form that any Dylan environment should
+ be able to understand. Dylan vendors have adopted LID to make it
easier to port applications from one environment to another. </p>
- <p>LID works by supplementing each set of library sources with a
- LID file. A <term>LID file</term> describes a Dylan library using
- a set of keyword statements. Together, these statements provide
- enough information for specifying and locating the information
- necessary to build a library from its source. This means all Dylan
- libraries designed for interchange consist of at least two files:
- a LID file, and one or more files containing the library source
- code. </p>
+ <p>Library interchange works by supplementing each set of library
+ sources with a <term>LID file</term>. A LID file describes a Dylan
+ library using a set of keyword statements. Together, these
+ statements provide enough information to specify the information
+ necessary to build a library from its source. This means that all
+ Dylan libraries designed for interchange consist of at least two
+ files: a LID file, and one or more files containing the library
+ source code. </p>
<p>Thus, a LID file performs a similar function to the
<filepath>Makefile</filepath> used in some C and C++ development
@@ -38,8 +38,9 @@
<p>LID files normally have the file extension
<filepath>.lid</filepath>.</p>
</conbody>
+
<related-links>
- <link href="../concept/lid-file-keywords.xml" type="reference"
format="xml">
+ <link href="../reference/lid-file-keywords.xml" type="reference"
format="xml">
<linktext>LID File Keywords</linktext>
</link>
<link href="dylan-file-naming-conventions.xml" type="reference"
format="xml">
--
Gd-chatter mailing list
Gd-chatter@xxxxxxxxxxxxxxxx
https://gauss.gwydiondylan.org/mailman/listinfo/gd-chatter
|
