> P.S.: Am even contemplating of using JNI (the Java native interface) > which possesses UTF-8 encodings/decodings out of the box, which means > that the dbus library would have to become a part of BSF4ooRexx. > Should ooRexx ever get UTF-8/Unicode capabilities I could adjust the > respective code then.
O.K. looked into this corner and will exploit BSF4ooRexx, if in a need to create UTF-8 strings or native strings from UTF-8 strings. It will be up to the Rexx programmer to take advantage of it. Then, should a UTF-8/Unicode capable version of ooRexx appear, one should be able to take advantage of it immediately. ---rony ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
