From: Mike Gran <spikegran@earthlink.net>
Subject: Trivial Documentation Path
Date: Mon, 02 Jun 2003 16:21:44 -0700 [thread overview]
Message-ID: <3EDBDC08.50808@earthlink.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
Here is a super-trivial document patch to the reference
manual.
Bug: punctuation error.
2000-05-02 Mike Gran spikegran@earthlink.net
* preface.texi: Minor punctuation mistakes. Hyphens
should link compound adjectives. Commas should be
placed after a "therefore" that begins a sentence.
Commas should not be used to separate a list of only 2
dependent clauses.
[-- Attachment #2: patch1 --]
[-- Type: text/plain, Size: 2512 bytes --]
*** preface.texi.orig Mon Jun 2 15:27:19 2003
--- preface.texi Mon Jun 2 15:51:54 2003
***************
*** 91,97 ****
introduction to the key ideas of the Scheme language --- and use of
Guile's @code{scm} interface to write new primitives and objects in C,
and to incorporate Guile into a C application. It also covers the use
! of Guile as a POSIX compliant script interpreter, and how to use the
Guile debugger.
@c @strong{Part V: Extending Applications Using Guile} explains the options
--- 91,97 ----
introduction to the key ideas of the Scheme language --- and use of
Guile's @code{scm} interface to write new primitives and objects in C,
and to incorporate Guile into a C application. It also covers the use
! of Guile as a POSIX-compliant script interpreter and how to use the
Guile debugger.
@c @strong{Part V: Extending Applications Using Guile} explains the options
***************
*** 109,117 ****
@strong{Part IV: Guile API Reference} documents Guile's core API. Most
of the variables and procedures in Guile's core programming interface
! are available in both Scheme and C, and are related systematically such
that the C interface can be inferred from the Scheme interface and vice
! versa. Therefore this part of the manual documents the Guile API in
functionality-based groups with the Scheme and C interfaces presented
side by side. Where the Scheme and C interfaces for a particular
functional area do differ --- which is sometimes inevitable, given the
--- 109,117 ----
@strong{Part IV: Guile API Reference} documents Guile's core API. Most
of the variables and procedures in Guile's core programming interface
! are available in both Scheme and C and are related systematically such
that the C interface can be inferred from the Scheme interface and vice
! versa. Therefore, this part of the manual documents the Guile API in
functionality-based groups with the Scheme and C interfaces presented
side by side. Where the Scheme and C interfaces for a particular
functional area do differ --- which is sometimes inevitable, given the
***************
*** 135,141 ****
@itemize @bullet
@item
! the POSIX module, which provides Scheme level procedures for system and
network programming that conform to the POSIX standard
@item
--- 135,141 ----
@itemize @bullet
@item
! the POSIX module, which provides Scheme-level procedures for system and
network programming that conform to the POSIX standard
@item
[-- Attachment #3: Type: text/plain, Size: 136 bytes --]
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2003-06-02 23:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 23:21 Mike Gran [this message]
2003-06-09 21:37 ` Trivial Documentation Path Marius Vollmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EDBDC08.50808@earthlink.net \
--to=spikegran@earthlink.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).