Best bet is wiki http://en.wikipedia.org/wiki/Computational_complexity_theory[^]

That means you didn't save it as Unicode .... What code are you using to write to the file ?

The best place to start is www.google.ca[^]

A bit more description would be more helpful but not as much as debugging the code, especially places that work with buffers ( strings etc) system managed handles (GDI objects, Global memory etc). Also:

od@ananzi.co.za wrote:

all in MS code, nothing else really that matters.

It is very possible that YOUR code uses win32 APIs incorrectly causing one of any number of possible leaks.

First about Unicode. There are two ways to store Unicode. E.g 'a' (ASCII) could be stored in Unicode like so: 0x61 0x00 or 0x00 0x61 How do you know the difference ? By storing a FE FF at the beginning of every Unicode string (this is called a Unicode Byte Order Mark) you know which way to read the bytes. Example: If I store 'a' in Unicode file I can have: FF FE 61 00 OR FE FF 00 61

Using Perl perl -pi -w -e 's/oldString/newString/g;' [place]

Short answer If your only targeting Windows platforms use CreateFile. Longer answer The main reason you would want to use the CRT functions (open() close() etc) is to make your program more portable there isn't any obvious advantage in speed or performance. That said, using win32 APIs does allows you to specify various parameters that CRT doesn't like Security attributes, Template file etc. It doesn't really matter what compiler you use in terms of the APIs you call the CRT you will use is the same regardless of the compiler used. That said I don't see a reason to use gcc to compile code for Windows.

In Visual Studio 2005: Click File->New->Project In the wizard under the visual C++ label you should have "MFC", then on the right side select the most suitable project type you need. When the wizard is finished hit F5 to compile and run your the test application Visual Studio generated for you. There should be buttons and sample text i believe. RM