----- Original Message ----- > I currently believe we need some kind of type
system in Squeak. It should
> probably be voluntary, to be used at the programmer's discretion. It
should
> express semantic intent as well as signature. It should honor
encapsulation.
>
> It could be fruitful to explore Traits as a typing system to be used to
> clarify complex logic and to be ignored in simple cases. For example, it
> could be used to define the provided interfaces of a Tweak Island, giving
a
> high level documentation of what the island does as well as enabling
> powerful tools for island composition. It could also be used to define the
> APIs of a package. (Many people in the Squeak community use the term "API"
> to mean something that does not include an explicit interface definition.
> This usage is very confusing to the uninitiated).
>
> Cheers
> --Trygve
>

One could define type-definitions in the header of a method or using the
browser..
Strongtalk gives an example, but seems a bit complicated...


Would indeed be nice to have more of a interface-management, instead of the
more static type-definitions..
Objects may "connect" only if they have the proper interfaces (or traits)..