summaryrefslogtreecommitdiff
path: root/doc/standards.texi
diff options
context:
space:
mode:
authorKarl Berry <karl@freefriends.org>2013-08-16 06:32:22 -0700
committerKarl Berry <karl@freefriends.org>2013-08-16 06:32:22 -0700
commit6f2d632522fd8a6277c75f5b8dfce96ed794236e (patch)
treeb785e2a5743023dc0ef13423ed38b67e1b394085 /doc/standards.texi
parent0ba087759d2797c8f7d3c34bef6268ba3fd212cb (diff)
downloadgnulib-6f2d632522fd8a6277c75f5b8dfce96ed794236e.tar.gz
autoupdate
Diffstat (limited to 'doc/standards.texi')
-rw-r--r--doc/standards.texi17
1 files changed, 11 insertions, 6 deletions
diff --git a/doc/standards.texi b/doc/standards.texi
index b18f4be038..6b4a00b6b6 100644
--- a/doc/standards.texi
+++ b/doc/standards.texi
@@ -3,7 +3,7 @@
@setfilename standards.info
@settitle GNU Coding Standards
@c This date is automagically updated when you save this file:
-@set lastupdate July 20, 2013
+@set lastupdate August 15, 2013
@c %**end of header
@dircategory GNU organization
@@ -295,9 +295,13 @@ speed, the best language to use is C. C++ is ok too, but please don't
make heavy use of templates. So is Java, if you compile it.
When highest efficiency is not required, other languages commonly used
-in the free software community, such as Python and Ruby, are ok too.
-We encourage use of Lisp and Scheme as well. Please implement the GNU
-configure and make interface no matter which language you use.
+in the free software community, such as Scheme, Python, Ruby, and
+Java, are OK too. Scheme, as implemented by GNU@tie{}Guile, plays a
+particular role in the GNU System: it is the preferred language to
+extend programs written in C/C++, and also a fine language for a wide
+range of applications. The more GNU components use Guile and Scheme,
+the more users are able to extend and combine them (@pxref{The Emacs
+Thesis,,, guile, GNU Guile Reference Manual}).
Many programs are designed to be extensible: they include an interpreter
for a language that is higher level than C. Often much of the program
@@ -3236,8 +3240,9 @@ the option @option{--quoting-style} of GNU @code{ls}.
@section Mmap
@findex mmap
-Don't assume that @code{mmap} either works on all files or fails
-for all files. It may work on some files and fail on others.
+If you use @code{mmap} to read or write files, don't assume it either
+works on all files or fails for all files. It may work on some files
+and fail on others.
The proper way to use @code{mmap} is to try it on the specific file for
which you want to use it---and if @code{mmap} doesn't work, fall back on