From: tomas@fabula.de
Subject: Strange behaviour of array?
Date: Tue, 5 Nov 2002 12:57:06 +0100 [thread overview]
Message-ID: <20021105115705.GA6539@www> (raw)
Hi,
while playing around with arrays (see my dumb questions in
guile-user) I stumbled across this:
| guile> (array? #f)
| #f
| guile> (array? 13)
| #f
| guile> (array? 'thisisasymbol)
| #t
| guile> (array? (list 1 2 3 4))
| #t
| guile> (array? 1.5)
| #f
| guile> (array? 3/4)
| #f
| guile> (array? +)
| #t
| guile> (array? 13228374653846507238652384)
| #f
It seems that many non-immediate values returns #t on array?. Looking
at the source (libguile/unif.c, around line 280) kind of semi-confirms
this (as far as I understand this tagging business).
This is against guile 1.6.0 as released (I haven't the time to check
now against CVS for lack of a suitable autoconf :-(
Regards
-- tomas
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2002-11-05 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-05 11:57 tomas [this message]
2002-11-15 8:12 ` Strange behaviour of array? Christopher Cramer
2002-11-15 8:46 ` tomas
2002-11-17 15:29 ` 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=20021105115705.GA6539@www \
--to=tomas@fabula.de \
/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).