all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org, "Eric M. Ludlam" <eric@siege-engine.com>
Subject: Re: EIEIO with lexical scoping
Date: Mon, 03 Jun 2013 14:35:28 -0400	[thread overview]
Message-ID: <usip1vdoun.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87sj0zusji.fsf@engster.org> (David Engster's message of "Mon, 03 Jun 2013 17:23:45 +0200")


>>> For instance, I had to change registry.el in Gnus, which for some
>>> reason had all 'defmethod' calls wrapped in 'eval-and-compile', which
>>> does not compile anymore. I don't know why, though; you probably
>>> do. ;-)
>>
>> I don't either, actually.

I suspect the following might be related; now `defclass' is opaque to
the byte-compiler. Compiling this:

(require 'eieio)

(defclass foo-class ()
  (())
  "blah.")

(defun foo-func ()
 (if foo-class
  (foo-class 'blah)))

warns:
  
  In foo-func:
  foo.el:8:7:Warning: reference to free variable `foo-class'
  
  In end of data:
  foo.el:9:1:Warning: the function `foo-class' is not known to be defined.

which is a bit annoying. It didn't use to do this. A total guess, maybe
the removal of `eval-and-compile' from defclass?



  reply	other threads:[~2013-06-03 18:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13 21:25 EIEIO with lexical scoping Stefan Monnier
2013-05-14  0:00 ` Eric M. Ludlam
2013-05-14  1:57   ` Eric M. Ludlam
2013-05-14  2:13   ` Stefan Monnier
2013-05-14 12:42     ` Stefan Monnier
2013-05-14 20:25     ` David Engster
2013-05-14 22:32       ` Stefan Monnier
2013-06-02 16:45       ` David Engster
2013-06-02 20:47         ` Stefan Monnier
2013-06-03 15:23           ` David Engster
2013-06-03 18:35             ` Glenn Morris [this message]
2013-06-03 19:35               ` Stefan Monnier

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=usip1vdoun.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=eric@siege-engine.com \
    --cc=monnier@IRO.UMontreal.CA \
    /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.