From: Stephen Compall <s11@member.fsf.org>
Subject: Re: doc ice-9 q
Date: 09 Jan 2004 10:48:35 -0600 [thread overview]
Message-ID: <xfyzncxxe3g.fsf@csserver.evansville.edu> (raw)
In-Reply-To: <87n08yf67u.fsf@zip.com.au>
Kevin Ryde <user42@zip.com.au> writes:
> Remove and return the front element from Q. If Q is empty, a
> `q-empty' exception is thrown.
Is said exception a proper error (i.e. with args KEY SUBR MSG ARGS
DATA)? If so, that ought to be said instead, along with what DATA is.
--
Stephen Compall or s11 or sirian
Paranoia doesn't mean the whole world isn't out to get you.
lock picking Juiliett Class Submarine Commecen industrial intelligence
embassy Rand Corporation Croatian SHA kilo class FBI sniper analyzer
electronic surveillance president CIDA
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-01-09 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 22:03 doc ice-9 q Kevin Ryde
2004-01-09 16:48 ` Stephen Compall [this message]
2004-01-10 19:43 ` Kevin Ryde
2004-01-11 0:18 ` 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=xfyzncxxe3g.fsf@csserver.evansville.edu \
--to=s11@member.fsf.org \
/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).