April 8, 2009
11:30 a.m.
lukas do you want that we produce a backward compatibility layer so that old seaside code loads in pharo?
No, I don't think it is necessary. The way builder.seaside.st creates the load scripts assuming that the compiler throws warnings for uppercase inst-vars only. However the closure compiler now also throws a warning when a variable is undeclared (yeah, there is at least one bug in Seaside2.9alpha3), whereas the previous compiler silently ignored it. I changed my exception handler to tell the compiler to ignore it as well (what is the default, when you don't catch warnings anyway). Lukas -- Lukas Renggli http://www.lukas-renggli.ch