unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: cedet-eieio@lists.sourceforge.net
Cc: "Eric M. Ludlam" <eric@siege-engine.com>, emacs-devel@gnu.org
Subject: Re: Cleaning up the EIEIO namespace
Date: Thu, 14 Feb 2013 17:17:50 -0500	[thread overview]
Message-ID: <jwvk3qak0cb.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87zjz6egb2.fsf@engster.org> (David Engster's message of "Thu, 14 Feb 2013 22:28:17 +0100")

>>> In toplevel form:
>>> eieio.el:168:1:Error: Symbol's function definition is void: eieio--class-parent
>> Can you (setq byte-compile-error t debug-on-error t) so as to get
>> a backtrace?
> Did you mean `byte-compile-error-on-warn'? Anyway, I'm afraid I just
> don't get a backtrace with debug-on-error.

No, I meant byte-compile-debug sorry.

>>> I also cannot find a definition for eieio--class-parent, but maybe it's
>>> hidden somewhere?
>> It's defined (as a macro) by the call to (eieio--define-field-accessors
>> class ...)  which is kind of a "mini cl-defstruct".
> I see. Now, I can compile your patched EIEIO with trunk, but using the
> latest pretest gives me the above error. I can fix this by including the
> define-field-accessor macro and its following two calls (for class and
> object) in the 'eval-and-compile' clause.  Not sure if that's the right
> thing to do, though.  Something must have changed in trunk in how this is
> handled?

Let me get back to you on this one, later,


        Stefan

------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb

  reply	other threads:[~2013-02-14 22:17 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10 18:10 Cleaning up the EIEIO namespace Stefan Monnier
2013-02-12 22:10 ` David Engster
2013-02-12 23:05   ` Drew Adams
2013-02-13  6:44     ` David Engster
2013-02-13 14:51       ` Drew Adams
2013-02-13  2:47   ` Stefan Monnier
2013-02-13 16:31     ` David Engster
2013-02-14  1:11       ` [cedet-eieio] " Eric M. Ludlam
2013-02-14 13:49         ` Stefan Monnier
2013-02-14 14:00           ` Xue Fuqiao
2013-02-14 21:17           ` David Engster
2013-02-14 22:16             ` Stefan Monnier
2013-02-18 21:32               ` David Engster
2013-02-19  3:26                 ` [cedet-eieio] " Stefan Monnier
2013-02-19 19:49                   ` David Engster
2013-02-19 21:55                     ` Stefan Monnier
2013-02-20 23:41                     ` [cedet-eieio] " Eric M. Ludlam
2013-03-29 10:04               ` Vitalie Spinu
2013-03-29 14:20                 ` Drew Adams
2013-03-29 21:07                 ` Stefan Monnier
2013-02-14 14:30       ` Stefan Monnier
2013-02-14 21:28         ` David Engster
2013-02-14 22:17           ` Stefan Monnier [this message]
2013-02-14 22:26             ` David Engster
2013-02-17 17:08               ` Stefan Monnier
2013-02-18 20:55                 ` David Engster
2013-02-19  3:15                   ` Stefan Monnier
2013-02-13  3:13   ` [cedet-eieio] " Eric M. Ludlam

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvk3qak0cb.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=cedet-eieio@lists.sourceforge.net \
    --cc=emacs-devel@gnu.org \
    --cc=eric@siege-engine.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).