Re: +initialize not called...

[Frederic Stark]

Jeff Teunissen wrote:

> Manuel Guesdon wrote:
>
> [snip]
>
>
> > Found the problem: a duplicate +initialize was defined in a
> > category in an other library. Removeing it solve the problem !
>
>
> Whoah, hold it...aren't all +initialize implementations, in all categories,
> supposed to be called (in an undefined order)?

AFAIK, this is true for +load, not for +initialize.

Cheers,

--fred