On Thu, 2010-02-11 at 10:43 +0100, Tobias C. Rittweiler wrote:
> Fredrik Tolf <fredrik@...> writes:
> > The warning I get is this:
> > [snip]
> > ; (SB-PCL::SET-SLOT-VALUE #:TMP37 'A #:NEW36)
> > ;
> > ; caught STYLE-WARNING:
> > ; undefined function: (SB-PCL::SLOT-ACCESSOR :GLOBAL A SB-PCL::WRITER)
> > [snip]
> For some reason, I can only reproduce the warnings on Linux x86-64 but
> not x86-32 (188.8.131.52 in both cases.)
> Are you on a 64bit system, too?
Nope, I'm on x86-32. When I try on a x86-64 machine, however, I get a
warning about the SB-PCL::READER function also being undefined.
> Is related but not quite the same. The above bug entry is about a case
> resulting in the same warning but even when an explicit type declaration
> is given.
I just discovered that, when I try the same code on an older version of
SBCL (the one from Debian Testing, 184.108.40.206), I get the warnings whether
I add the type declaration or not. It is only on the SBCl from Debian
Unstable, 220.127.116.11, that I can avoid them by adding type declarations.
It may be worth mentioning that the x86-64 machine I was trying on is
running Debian Stable, which has SBCL 18.104.22.168. Seeing how the amount of
warnings seems to be decreasing over the increasing SBCL versions, might
that mean that this is being fixed in SBCL?