all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: How to silence "Unknown slot" compiler warnings?
Date: Tue, 16 Feb 2016 08:51:57 -0600	[thread overview]
Message-ID: <86mvr0iu7m.fsf@stephe-leake.org> (raw)
In-Reply-To: <87wpq4eo6n.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Tue, 16 Feb 2016 22:15:44 +0800")

Eric Abrahamsen <eric@ericabrahamsen.net> writes:

> On 02/16/16 10:58 AM, Vitalie Spinu wrote:
>>>> On Tue, Feb 16 2016 13:38, Eric Abrahamsen wrote:
>>
>>> You're using oref/oset with arguments as :tags, but the slot name should just
>>> be a non-quoted, non-tag macro argument.
>>
>> What is this restriction for?
>>
>> That's the whole point of :initarg AFAIC. I need to use keywords to enhance
>> readability of the code. There quite a few slots in my package and I want to
>> distinguish then from local and global vars.
>
> Initargs are still tags and only tags. But slot reference is only a
> "naked" slot name (with oref/oset), or else a quoted symbol (with
> eieio-{oref,oset}, or slot-value and set-slot-value). oref and oset are
> just thin wrappers around the eieio-* versions.
>
> I can't say why! I'm also a little uncomfortable about the "naked"
> versions, and for the same reason -- my brain keeps seeing them as
> variables.

More importantly, it's a change from Emacs 24, that breaks a lot of
existing code.

Does this change make eieio consistent with some standard?

-- 
-- Stephe



  reply	other threads:[~2016-02-16 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-15 20:15 How to silence "Unknown slot" compiler warnings? Vitalie Spinu
2016-02-15 21:13 ` Stephen Leake
2016-02-16  0:22   ` Vitalie Spinu
2016-02-16  5:38     ` Eric Abrahamsen
     [not found]       ` <871t8dase0.fsf@gmail.com>
2016-02-16 14:15         ` Eric Abrahamsen
2016-02-16 14:51           ` Stephen Leake [this message]
2016-02-21  2:05     ` Stefan Monnier
2016-02-21  4:13       ` Eric Abrahamsen

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=86mvr0iu7m.fsf@stephe-leake.org \
    --to=stephen_leake@stephe-leake.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.
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.