I seem to recall hearing (from the GNU Smalltalk author) that the text representation of Smalltalk isn't even standard. See http://www.gnu.org/software/smalltalk/manual/html_node/Synta..., for example.
Re:Smalltalk: Welcome to the Balkans
by spooneybarger on Thursday February 11, 2010 @05:06PM
(#1118892)
Why would it be suprising that there isn't a standard text file representation of something that is hardly ever represented that way?
Why? Well, smalltalk didn't always have nice OO code management tools. You used to have a good handle on your "changes" and "sources" files. At one point (early '90s), it was not a problem to take code from a text file you "filed-out" in Digitalk smalltalk and "file-in" the same text in ParcPlace's smalltalk.
In those days, there were only two good ways to "version" your code: 1 - copy the entire image pared with "changes" and "sources" files; 2 - "file-out" some or all of your code to a text file. I did this often. It is fair to say that less professional developers did not do this, but that's no different than today's developers that don't use any form of version control.
Re:Smalltalk: Welcome to the Balkans
by spooneybarger on Thursday February 11, 2010 @04:47PM
(#1118859)
You can file code in and out of every smalltalk I've ever used. Its just a pain compared to getting an image. Or on most smalltalks now, you can just load monticello packages in ( its a smalltalk code & object distributed versioning system ).
While file in and out is a pain for large amounts of code, monticello and metacello make bringing code in and out of an image quite easy.
An exception got thrown? The code browser takes you to the method that did it. You fix the error, and repeat the action that triggered the exception, and since the application doesn't completely die, you only need to repeat the last step.
It's crazy ... with the obvious disadvantage that it's hard to export / import source-code. That's why frameworks are distributed as already built images.