Re: How do I write directly to a memory address?

[Georg Bauhaus <rm-host.bauhaus@maps.futureapps.de>]

On 3/2/11 10:45 AM, Nasser M. Abbasi wrote:

> ----------------------------
> swith(clientID){
> case "eStore":
> callEStore();
> break;
> case "Retail":
> calRetail();
> break;
> case "CSR":
> callCSR();
> break;
> default:
> invalidClient();
> }
> -----------------------
>
> It seems like it might be a convenient feature?

The feature is present in Eiffel and C#.  The syntax looks nicely
clean, compared to repeated ifelse.  Is it healthy in practice?
If a convenience, and welcome as such, what kinds of programs
will the feature make more likely when in the hands of programmers?

With Java 5 enumeration types, you can already link strings and
methods to enumeration literals. And then still use enums, not
strings, for making distinctions.  If Java 5 were Ada, a Java
programmer could then switch on an enum and be sure that all cases
are covered specifically (no "others" or "default").  This cannot
be achieved with an untyped selection of strings (i.e. not some
type's set of strings), since no case coverage is possible.

You might also end up with two kinds of string literals in your
Java program, but not with two types, since there is only one
for string literals:

(1) Strings that can be "internationalized" and
(2) strings that can't because they control program logic in some
    switch statement.

Or can you switch natural languages while the Java program is
running and still assume that the switch {} will be working as
it should? Can the translation of the switch still be efficient?

Granted, similar issues can affect ifelse, e.g. when a
translation produces the same word W for two different words
W1 and W2 of the original language.

Conclusion:

controlling program flow by inspecting string values creates
maintenance effort and program translation issues caused by
the absence of distinguished types.