unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: 30145@debbugs.gnu.org
Subject: bug#30145: [PATCH] doc: Document unspecified?.
Date: Thu, 18 Jan 2018 11:50:29 +0530	[thread overview]
Message-ID: <20180118062029.5655-1-arunisaac@systemreboot.net> (raw)
In-Reply-To: <20180117175204.1381-1-arunisaac@systemreboot.net>

* doc/ref/data-rep.texi: Document unspecified?.
---
 doc/ref/data-rep.texi | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/doc/ref/data-rep.texi b/doc/ref/data-rep.texi
index bb7f74afe..f179a3560 100644
--- a/doc/ref/data-rep.texi
+++ b/doc/ref/data-rep.texi
@@ -470,6 +470,9 @@ check to see if @var{x} is @code{SCM_UNBOUND}.  History will not be kind
 to us.
 @end deftypefn
 
+@deffn {Scheme Procedure} unspecified? x
+Return @code{#t} if @var{x} is unspecified, else @code{#f}.
+@end deffn
 
 @node Non-immediate objects
 @subsubsection Non-immediate objects
-- 
2.15.1






  parent reply	other threads:[~2018-01-18  6:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-17 17:52 bug#30145: [PATCH] doc: Document undefined? Arun Isaac
     [not found] ` <handler.30145.B.15162115551614.ack@debbugs.gnu.org>
2018-01-18  6:16   ` bug#30145: Acknowledgement ([PATCH] doc: Document undefined?.) Arun Isaac
2018-01-18  6:20 ` Arun Isaac [this message]
2018-01-21 14:48   ` bug#30145: [PATCH] doc: Document unspecified? Mark H Weaver
2018-01-21 18:22     ` Arun Isaac
2018-01-21 14:33 ` bug#30145: [PATCH] doc: Document undefined? Mark H Weaver

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=20180118062029.5655-1-arunisaac@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=30145@debbugs.gnu.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).