----- "Lukas Renggli" <[email protected]> wrote: | > And, I also agree with lukas. blahDo: is ugly, if you have an | elegant | > solution... but, what I have to do with OB-Tools? I replace methods | > (like before) or better I create a package OB-Tools-Squeak with | > extensions for Squeak? | | I guess the best is to follow the Seaside coding conventions | (http://www.seaside.st/community/conventions) for cross platform code | like OB-Tools. You might also want to use Slime | (http://www.lukas-renggli.ch/blog/slime), because it automatically | fixes simple issues like the #ifNotNilDo: thing. Also keep in mind | that OB-Tools is supposed to run on GemStone , so better not use | #ifNotNilDo:.
I introduced this incompatibility in my recent bugfixes for the debugger in OB-Tools, so the code in question is in a Squeak/Pharo specific chunk... Since I work in GemStone most of the time, I wasn't aware of the differences #ifNotNil:...:) You'll see more '== nil' in my code from now on:) Dale _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
