From: Kevin Ryde <user42@zip.com.au>
Subject: doco error key indexing
Date: Sat, 10 May 2003 11:17:43 +1000 [thread overview]
Message-ID: <87u1c3siq0.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 105 bytes --]
FYI, I made this change
* scheme-control.texi (Handling Errors): Index entries for error keys.
[-- Attachment #2: scheme-control.texi.error-index.diff --]
[-- Type: text/plain, Size: 1502 bytes --]
--- scheme-control.texi.~1.7.~ 2003-05-09 16:27:52.000000000 +1000
+++ scheme-control.texi 2003-05-10 11:13:52.000000000 +1000
@@ -894,40 +894,50 @@
@itemize @bullet
@item
+@cindex @code{error-signal}
@code{error-signal}: thrown after receiving an unhandled fatal signal
such as SIGSEGV, SIGBUS, SIGFPE etc. The @var{rest} argument in the throw
contains the coded signal number (at present this is not the same as the
usual Unix signal number).
@item
+@cindex @code{system-error}
@code{system-error}: thrown after the operating system indicates an
error condition. The @var{rest} argument in the throw contains the
errno value.
@item
+@cindex @code{numerical-overflow}
@code{numerical-overflow}: numerical overflow.
@item
+@cindex @code{out-of-range}
@code{out-of-range}: the arguments to a procedure do not fall within the
accepted domain.
@item
+@cindex @code{wrong-type-arg}
@code{wrong-type-arg}: an argument to a procedure has the wrong type.
@item
+@cindex @code{wrong-number-of-args}
@code{wrong-number-of-args}: a procedure was called with the wrong number
of arguments.
@item
+@cindex @code{memory-allocation-error}
@code{memory-allocation-error}: memory allocation error.
@item
+@cindex @code{stack-overflow}
@code{stack-overflow}: stack overflow error.
@item
+@cindex @code{regex-error}
@code{regex-error}: errors generated by the regular expression library.
@item
+@cindex @code{misc-error}
@code{misc-error}: other errors.
@end itemize
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2003-05-10 1:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87u1c3siq0.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).