On Thu, Sep 13, 2012 at 11:51 PM, Camillo Bruni <[email protected]>wrote:

> We still have a very nasty compiler bug open for 2.0
>         https://code.google.com/p/pharo/issues/detail?id=6601
>
> The bug currently blocks all loading of configurations, since
> all references to previously undefined classes are not properly
> resolved => Compiler recompileAll is currently the only solution.
>
> Does anybody know where the undefined globals are handled?
> Otherwise I'll dig into it tomorrow morning...
>
>
The change in the warningAllowed may have changed stuff. See Encoder >>
#undeclared.
The value of warningAllowed changes the IF and the possible paths.
Compare that method with 1.4 ;)

Cheers



-- 
Mariano
http://marianopeck.wordpress.com

Reply via email to