[Seaside-dev] WAVirtualMachineStatus>>#renderValuesOn:

[Esteban Lorenzano]

yeah… that’s kinda annoying… warnings should never be blocking. 
but that’s the way they always worked in pharo and I think before too… I would be willing to change that behaviour (for pharo4, we are too close to a release now), if we came up with an idea :)

Esteban

On 17 Feb 2014, at 09:54, Johan Brichau <johan at inceptive.be> wrote:

> 
> On 17 Feb 2014, at 09:53, Esteban Lorenzano <estebanlm at gmail.com> wrote:
> 
>> there is also a setting in Pharo to disable the blocking dialog. 
>> 
>> Deprecation raiseWarning: false.
> 
> We know.
> It's just that nobody disables it, so everyone gets errors instead of deprecation warnings.
> 
> Johan_______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev