Re: [Sbcl-devel] "bad thing to be a type specifier" error on threaded usage

[Nathan F. <fr...@gm...>]

On 11/6/07, Nikodemus Siivola <nik...@ra...> wrote:
> On 11/5/07, Attila Lendvai <att...@gm...> wrote:
> > some more info: i've studied SB-C::SET-INFO-VALUE and it seems to me
> > that it's missing a lock. i've checked what the info db's structure
> > is, and it doesn't seem to be a thread-safe structure to me, so i
> > suspect this to be the cause of problem.
> >
> > fyi, contextl is calling ENSURE-CLASS as layers are enabled/disabled.
>
> This is going to take a fair amount of work to make it work, I'm afraid:
> when you change the class hierarchy you basically cannot have
>
> [lots of things you can't do]

Are you saying "If we added proper locking in SET-INFO-VALUE, these
things would suffer"?  Or "Even with proper locking in SET-INFO-VALUE,
these things would still be impossible"?  Or something else entirely?

-Nathan