Re: How to silence "Unknown slot" compiler warnings?

[Eric Abrahamsen]

Stefan Monnier <address@hidden> writes:

[...]

>> 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.
>
> The "naked" version only shows up with (oref x hostmode) which is an
> EIEIO-only macro which is equivalent to (slot-value x 'hostmode).
> As you can see, the (slot-value x 'hostmode) version doesn't suffer from
> this problem (and additionally it's part of CLOS), so I encourage you to
> use that instead.
> EIEIO can't take advantage of the compile-time-knowledge of `hostmode'
> to speed up the slot access anyway, so you might as well use `slot-value'.

Thanks! It's good to have a clear answer to that.