You had expressed concern about code having a dependence on categories
/ protocols.  You wrote:

> Part of this discussion is related to tools. Message categories are just too
> easy to change. How many of you do "full text search" or "string search" any
> time they add/remove/change a message category?

I assumed your concern was that we don't have any tools to "alert us"
if a message category which is depended on by code, would be changed.

SUnit and its tools allows this sort of late-binding to be feasible.
We use it to assert what certain behaviors *should* be.  i.e., we
could add a test to require teh presence of certain protocols.

Or, even better, maybe some startup method on class-side could simply
ensure the necessary protocols would be present (creating them, if
necessary) to address Berts concern about stripping sources (does that
strip protocols too?).

<pine>We've heard Java advocates use the marketing phrase "type safe"
but we know "safe" is misleading.  The app could still have a
NullPointnerException, DivideByZero, FileNotFound, etc.  So they
actually just need JUnit more than they need early-binding.  Yes,
early-binding supports better code-completion tool but... the rest is
pure cost, IMHO).</pine>

Best,
  Chris

On Thu, Apr 14, 2016 at 2:49 AM, marcel.taeumel <Marcel.Taeumel at hpi.de> wrote:
> Hi Chris,
>
> I am not exactly sure what you mean by that but yes: we can write a test for
> that. :-) Or are you referring to the test* prefix in test selectors?
>
> Best,
> Marcel
>
>
>
> --
> View this message in context: http://forum.world.st/The-Inbox-Collections-CW-640-mcz-tp4889722p4889841.html
> Sent from the Squeak - Dev mailing list archive at Nabble.com.
>