Hi Janko!<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
<br>
</div>I'm not quite sure that you can make Unicode support optional, that is,<br>
loadable as a separate package. Unicode is roughly made of two things:<br>
</blockquote><div><br>There is also another issue: complexity. Loadable things are often far to be straightforward as it may seem: you often end up in having mutually excluding loadable packages. OTOH a multi-byte string is less performing than a single-byte string and many users who live in the ASCII side of the planet may not be willing to pay the performance fee.<br>
<br>But... this is SmallTalk, isn't it? Why can't we load the unicode thing everywhere and use polymorphism so that if I load ASCII data it performs as ASCII data? It sounds more like SmallTalk to me. And a thing that is everywhere is usually much better debugged.<br>
<br>Berto<br></div></div><br>