From: MON KEY <monkey@sandpframing.com>
To: 6878@debbugs.gnu.org
Subject: bug#6878: bool-vectors of length 0 signal error when aref/aset the 0th element
Date: Thu, 19 Aug 2010 10:13:42 -0400 [thread overview]
Message-ID: <AANLkTimEZqsnK=s2ySmW2MWNd9-rRRhzgRSvRQZhyZT5@mail.gmail.com> (raw)
In-Reply-To: <m3vd779ep1.fsf@hase.home>
On Thu, Aug 19, 2010 at 4:42 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:
>> ,---- (info "(elisp)Bool-Vector Type")
>> |
>> | "A "bool-vector" is a one-dimensional array of elements that must be `t'
>> | or `nil'."
>
> All elements of (make-bool-vector 0 t) are either t or nil.
>
Prove it!
Please provide one piece of code that explicitly allows accessing the
`t' at elt 0 and/or distinguishing whether the elt at idx 0 is either
`t' or `nil'.
I can't find a way to do it. Can you?
In the absence of a working example I think you have a bug on your hands.
> Andreas.
--
/s_P\
next prev parent reply other threads:[~2010-08-19 14:13 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 4:19 bug#6878: bool-vectors of length 0 signal error when aref/aset the 0th element MON KEY
2010-08-18 7:36 ` Stefan Monnier
2010-08-19 1:51 ` MON KEY
2010-08-19 8:42 ` Andreas Schwab
2010-08-19 14:13 ` MON KEY [this message]
2010-08-19 15:51 ` Stefan Monnier
2010-08-19 17:06 ` MON KEY
2010-08-19 14:47 ` Stefan Monnier
2010-08-19 15:04 ` Andreas Schwab
2010-08-19 16:18 ` Chong Yidong
2010-08-19 17:09 ` MON KEY
2010-08-19 18:40 ` Juanma Barranquero
2010-08-19 23:24 ` Chong Yidong
2010-08-20 2:01 ` MON KEY
2010-08-20 2:23 ` Juanma Barranquero
2010-08-20 18:01 ` MON KEY
2010-08-20 19:49 ` Juanma Barranquero
2010-08-20 23:06 ` MON KEY
2010-08-20 13:02 ` Stefan Monnier
2010-08-20 18:44 ` MON KEY
2010-08-21 12:40 ` Kevin Rodgers
2010-08-21 15:53 ` Andreas Schwab
2010-08-21 17:02 ` MON KEY
2010-08-18 8:36 ` Andreas Schwab
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTimEZqsnK=s2ySmW2MWNd9-rRRhzgRSvRQZhyZT5@mail.gmail.com' \
--to=monkey@sandpframing.com \
--cc=6878@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.