--- In [email protected], "entropyreduction" <alancampbelllists+ya...@...> wrote: > > I could easy add config ini keys checkForUnicodeArgs, > checkForUnicodeResult. All or nothing, either checking happens or > it doesn't (obviously if I can;t locate unicode plugin, checking > never happens).
I suppose ini could house defaults, although personally I think default should always be ANSI. But in scripts we could do something like: e.g., com.returnUnicodestrings(1) and com.returnUnicodestrings(0) and similar for enabling/disabling checking for unicode args. I no longer think you should "check" for unicode results char>255. If the script wants to treat the returned string as unicode, it should be possible to do so (regardless if only low value characters are used). Also I don't think com should automatically load the unicode plugin. If the user wants to load the unicode plugin, it is easily done, e.g., with unicode.version. If com.returnUnicodestrings(1) and unicode is not already loaded, generate an error. (I seem to remember Bruce added something that makes it possible to test if a plugin is loaded). If unicode is not loaded, and checking for unicode arguments is enabled, arguments cannot really be in unicode; just send the strings. > Okay, other topic. Whenever I retrun an object (com handle) from > method, get, I set com_type to "object". It could be, instead, > the name I retrieve from GetDocumentation One step further: at > the moment don;t set com_type for create_object, get_object. I > could, filling it with same name (I've tried it, object name is > nothing like the "Scripting.FileSystemObject" monikers used to > access object). Sounds like that might make com_type more useful. Regards, Sheri
