"Richard A. O'Keefe" ok@cs.otago.ac.nz wrote:
Helge.Horch@t-online.de (Helge Horch) provided LessPvt.1.cs.
Ta muchly.
Anyone read the paper about Smalltalk collections in OOPSLA 92?
I googled that you probably meant William R. Cook's "Interfaces and Specifications for the Smalltalk-80 Collection Classes", and CiteSeer was able to come up with a location on the web. A *very* interesting read indeed.
That's the one.
Cook's work on cleaner specification of the Collection classes was incorporated into the Strongtalk libraries. The Extensible protocol I mentioned earlier is an example of that. Since I had a type system at my disposal, I was also able to do a lot more formal verification of signature compatibility in the hierarchy. Additionally, lots of semantic substitutability cleanups were made, that go beyond the typing issues.
So if anyone is interested in what an actual implementation of such a cleaner heirarchy would look like, it is right there in Strongtalk (and is freely borrowable, as well).
Cheers, Dave
Hi David,
Would someone be kind enough to produce ascii-text (or at least non-binary) versions of the Strongtalk sources, since I don't have a readily-handy new Windows machine, and the Strongtalk system is totally unusable on older Windows versions? (I gave up after the hundredth blue screen.)
I'm working on a new language, and want to incorporate the best ideas that I can into my collection hierarchy. I've already ported and augmented, trimmed, and modified Squeak's collection types, but without real access to Strongtalk, there are some aspects of this that aren't apparent.
TIA, ~
On Fri, 30 Aug 2002, David Griswold wrote:
"Richard A. O'Keefe" ok@cs.otago.ac.nz wrote:
Helge.Horch@t-online.de (Helge Horch) provided LessPvt.1.cs.
Cook's work on cleaner specification of the Collection classes was incorporated into the Strongtalk libraries. The Extensible protocol I mentioned earlier is an example of that. Since I had a type system at my disposal, I was also able to do a lot more formal verification of signature compatibility in the hierarchy. Additionally, lots of semantic substitutability cleanups were made, that go beyond the typing issues.
So if anyone is interested in what an actual implementation of such a cleaner heirarchy would look like, it is right there in Strongtalk (and is freely borrowable, as well).
Cheers, Dave
squeak-dev@lists.squeakfoundation.org
-
Brian T Rice -
David Griswold