From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Cc: ding@gnus.org
Subject: Re: bizarre byte-compile issue, possibly due to EIEIO
Date: Tue, 05 Apr 2011 13:44:00 -0500 [thread overview]
Message-ID: <874o6c4jyn.fsf@lifelogs.com> (raw)
In-Reply-To: <87aag4mtx2.fsf@randomsample.de>
On Tue, 05 Apr 2011 20:31:37 +0200 David Engster <deng@randomsample.de> wrote:
DE> Ted Zlatanov writes:
>> On Tue, 05 Apr 2011 18:38:23 +0200 David Engster <deng@randomsample.de> wrote:
>>
DE> I saw that you now set every slot value in the :after method. This isn't
DE> necessary; :initform is absolutely save to use for symbols. The only
DE> thing that changed in EIEIO is for the case where :initform is a
DE> function which has to be evaluated, which is only working correctly in
DE> newer versions.
>>
>> I thought it was more consistent to set all the slot values in one
>> place. It is more verbose though... I'm 50-50 on it, do you see any
>> issues with the method other than being more verbose?
DE> I just wanted to make clear that aside from function evaluations there's
DE> no issue with using :initform. I think :initform is better for
DE> documentation purposes (it will be shown as "default" in
DE> describe-function, although that seems to be currently broken in
DE> Emacs24), and it's also better in case you want to allow users to
DE> customize objects using eieio-customize. Otherwise, it's more a matter
DE> of style. I think constructors should be used to create somewhat
DE> "dynamical" objects.
OK, I've put the initforms back. Thanks for the help!
Ted
next prev parent reply other threads:[~2011-04-05 18:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87hbahww99.fsf@lifelogs.com>
2011-04-02 0:54 ` Ted Zlatanov
2011-04-02 20:34 ` Lars Magne Ingebrigtsen
2011-04-04 13:47 ` Ted Zlatanov
2011-04-04 15:26 ` David Engster
2011-04-02 21:32 ` David Engster
2011-04-03 9:34 ` David Engster
2011-04-04 10:18 ` Ted Zlatanov
2011-04-04 15:34 ` David Engster
2011-04-05 15:56 ` Ted Zlatanov
2011-04-05 16:38 ` David Engster
2011-04-05 17:55 ` Ted Zlatanov
2011-04-05 18:31 ` David Engster
2011-04-05 18:44 ` Ted Zlatanov [this message]
2011-04-05 16:14 ` Ted Zlatanov
2011-04-05 17:57 ` Ted Zlatanov
2011-04-04 16:29 ` 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=874o6c4jyn.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
--cc=emacs-devel@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.
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 NNTP newsgroup(s).