On Wed 11 Jan 2012 18:53, Daniel Llorens writes:
> I've found an bug in array output. It's peculiar. I haven't tried to
> debug it or bisect it, hopefully it rings a bell somewhere. It only
> happens when the rank of the array is not 1. This was tested in the
> last stable-2.0 (bbe34).
How embar
The GNU coding standards advise sticking with proper case for
identifiers, even if the identifier starts with a lowercase letter and
appears at the beginning of a sentence.
The Guile manual seems to follow this convention, with the exception of
r5rs.texi, hence the attached patch.
>From 811ad499d
Hi-
There's a bit of confusion on the guile-config deprecation.
NEWS says that guile-config "will be deprecated"
meta/guile-config.in says it "has been deprecated"
meta/guile.m4's GUILE_PROGS rule will error "guile-config required
but not found"
likewise those rules that depend on GUILE_PROGS,
According to the documentation, the module-name in define-module is of
the form (hierarchy file).
However, one can do (define-module (foo)).
Whenever eof is reach in a port, a call to unread-char passing eof
triggers an error. I'm not sure what's the right behavior for this,
but I guess the way it is now is just as the user should be
responsible to check eof.
A note in the documentation would help in any case.
The links for "Normal Termination" and "Termination Internals" are
invalid. Should be, respectively:
http://www.gnu.org/savannah-checkouts/gnu/libc/manual/html_node/Normal-Termination.html
http://www.gnu.org/savannah-checkouts/gnu/libc/manual/html_node/Termination-Internals.html
