mirror of
https://git.savannah.gnu.org/git/guile.git
synced 2025-05-20 11:40:18 +02:00
Fix incorrect uses of en-dashes and em-dashes in the intro.
* doc/ref/intro.texi (Introduction): Use commas instead of en-dashes around "for example". Use em-dashes instead of en-dashes around parenthetical phrases. Remove spaces around em-dashes.
This commit is contained in:
parent
cdd47ec7e5
commit
f0c56cadfd
1 changed files with 7 additions and 7 deletions
|
@ -19,7 +19,7 @@ Revised^n
|
|||
@end ifnottex
|
||||
Reports on Scheme).
|
||||
|
||||
Unlike -- for example -- Python or Perl, Scheme has no benevolent
|
||||
Unlike, for example, Python or Perl, Scheme has no benevolent
|
||||
dictator. There are many Scheme implementations, with different
|
||||
characteristics and with communities and academic activities around
|
||||
them, and the language develops as a result of the interplay between
|
||||
|
@ -74,7 +74,7 @@ world.
|
|||
The Scheme community has recently agreed and published R6RS, the
|
||||
latest installment in the RnRS series. R6RS significantly expands the
|
||||
core Scheme language, and standardises many non-core functions that
|
||||
implementations -- including Guile -- have previously done in
|
||||
implementations---including Guile---have previously done in
|
||||
different ways. Guile has been updated to incorporate some of the
|
||||
features of R6RS, and to adjust some existing features to conform to
|
||||
the R6RS specification, but it is by no means a complete R6RS
|
||||
|
@ -109,9 +109,9 @@ This kind of combination is helped by four aspects of Guile's design
|
|||
and history. First is that Guile has always been targeted as an
|
||||
extension language. Hence its C API has always been of great
|
||||
importance, and has been developed accordingly. Second and third are
|
||||
rather technical points -- that Guile uses conservative garbage
|
||||
rather technical points---that Guile uses conservative garbage
|
||||
collection, and that it implements the Scheme concept of continuations
|
||||
by copying and reinstating the C stack -- but whose practical
|
||||
by copying and reinstating the C stack---but whose practical
|
||||
consequence is that most existing C code can be glued into Guile as
|
||||
is, without needing modifications to cope with strange Scheme
|
||||
execution flows. Last is the module system, which helps extensions to
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue