> The rationale is that there is no dependably common case. This is true or false depending upon the scope of code your examining.
If your scope is the entire Factor repository, then of course there will be a variety of encodings in use. If you limit your scope to a single vocabulary, or even a hierarchy of vocabularies comprising a particular application, then it will be commonplace to use the same "text" encoding throughout. At any given time, this is precisely the scope which a programmer is focused on. In this case, the api fights with you because you have to state the encoding each time you deal with file or process streams, unless you were *forced* to factor out this silliness. Changing the encoding using dynamic scope would solve the second case. Ed ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Factor-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/factor-talk
