-
I suggest that all OWL input and output files are treated as ANSI for the following reasons:
1. This is what the iostreams library does.
2. It keeps backward compatibility with existing code.
It would be great if there was a mechanism if the streams could be imbued with a suitable codecvt facet to allow streams to be read and written in any code page (which would include UTF8, UTF16...
2009-11-14 18:45:44 UTC in OWL Next: C++ Object Oriented Framework
-
Whoops! Sorry the Markdown parser made a bit of a pigs ear of that didn't it!
2009-11-05 21:34:57 UTC in OWL Next: C++ Object Oriented Framework
-
I have been hacking around to step13 from the OWL tutorial series to work with Visual C++ 2008 in Unicode and with BI_NOINCLUDE_NS_OWL defined.
I have found it necessary to apply the following patches to the OWL sources. I know that unicode iostreams only write non-unicode files but the bug seems more subtle than that. Any tips on how to fix this problem? Incidentally the link to the tutorial...
2009-11-05 21:29:46 UTC in OWL Next: C++ Object Oriented Framework
-
Thanks Jogy,
Your fix works a treat.
Paul.
2009-11-02 19:21:31 UTC in OWL Next: C++ Object Oriented Framework
-
OK, I have resolved the first problem by setting the entry point in the linker to "wWinMainCRTStartup" as recommended on this site but the second problem still occurs.
2009-11-01 20:21:39 UTC in OWL Next: C++ Object Oriented Framework
-
I have successfully built OWLNext 630.2 with Visual C++ 2008 and with non-Unicode OWLDLL builds my application works fine. However when building for unicode I get two problems:
1. I have to implement my own _tWinMain function otherwise a linker error occurs. Having implemented the _tWinMain function,
2. When my application throws a TXOWL exception it seems a stack corruption occurs and the...
2009-10-31 22:01:43 UTC in OWL Next: C++ Object Oriented Framework
