[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#16153: closed (24.3.50; (gv-ref (car (cdr x))) =>

From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#16153: closed (24.3.50; (gv-ref (car (cdr x))) => strange expression)
Date: Mon, 16 Dec 2013 19:13:02 +0000

Your message dated Mon, 16 Dec 2013 14:11:55 -0500
with message-id <address@hidden>
and subject line Re: bug#16153: 24.3.50; (gv-ref (car (cdr x))) => strange 
has caused the debbugs.gnu.org bug report #16153,
regarding 24.3.50; (gv-ref (car (cdr x))) => strange expression
to be marked as done.

(If you believe you have received this mail in error, please contact

16153: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16153
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.3.50; (gv-ref (car (cdr x))) => strange expression Date: Sun, 15 Dec 2013 07:29:05 +0100

Sorry if I speak nonsense, but that doesn't make sense to me:

(setq x '(1 (2 3) 4))

(setq ref (gv-ref (car (cdr x))))

   ((lambda nil
     (car #1=#:v))
    (setcar #1# gv--val))

(gv-deref ref)

Symbol's value as variable is void: #:v

Seems like `gv-letplace' is constructing an illegitimate expression with
a free variable here.



In GNU Emacs (x86_64-unknown-linux-gnu, GTK+ Version 3.8.4)
 of 2013-11-13 on drachen
Windowing system distributor `The X.Org Foundation', version 11.0.11403000
System Description:     Debian GNU/Linux testing (jessie)

Configured using:
 `configure --prefix=/usr/local/built/'

Important settings:
  value of $LC_ALL: de_DE.utf8
  value of $LC_COLLATE: C
  value of $LC_TIME: C
  value of $LANG: de_DE.utf8
  locale-coding-system: utf-8-unix
  default enable-multibyte-characters: t

--- End Message ---
--- Begin Message --- Subject: Re: bug#16153: 24.3.50; (gv-ref (car (cdr x))) => strange expression Date: Mon, 16 Dec 2013 14:11:55 -0500 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)
>> In general, `gv-ref' only works with lexical-binding.
> I see.  Maybe say this somewhere - in the doc string, or at least in the
> source code.  It's IMHO not obvious (or is it?).

I added a note in the docstring, thank you,


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]