How compatible with [VisualWorks, VisualAge, Smalltalk/X, Dolphin, etc] Smalltalk will the code examples be?
Though I’m not writing these articles with code portability in mind, and I’m not doing any portability testing, much of the basic code should be compatible. By basic code, I mean things like how collections are used, how classes are declared, instance variable use, etc. Traditionally where the different flavours of Smalltalk differ most is in GUI code. With Squeak specifically, some of the cool stuff we’re going to look at isn’t portable to other flavours, for example: the halo stuff, morphic stuff, and downloading projects. What I’ll start doing though, is any code that I a priori suspect is Squeak specific, I’ll tag with [Squeak-only-suspected]. NOTE: this will only indicate my suspicion – I don’t plan on spending time on testing it in different flavours, or searching for ways to accomplish the same task in a different manner. This would be a great use of the Linux Gazette’s talkback sections – if other Smalltalkers note what does and doesn’t work in other flavours, they can post thi
