Hi Przemek, > Sorry but I do not understand why do you want to delete > already working code. > In longer terms it may cause that we will create problems > for platform which do not use Unicode forcing Unicode everywhere > reducing Harbour functionality to current Java or Phyton level. > For me it will be end of this project.
Perhaps you misunderstood me, but I'm not saying to "force" unicode "everywhere". Only on Windows API calls in Windows specific code parts. This has nothing to do with Harbour core functionality, which can continue to support everything it supported thus far. The reason for my initiative is that we have quite limited resources, and if you ask me, I used to spend lots and lots of time to make code work in both modes (not to mention the other variation on Windows platforms). Even this lots of time is not enough to test it properly, as practice shows. I'd assume the same is even more true in your case. We have 200 '#ifdef UNICODE' branching in Harbour codebase, which is quite a lot. Not to mention other developers who'd like to contribute; very few ppl can provide code which doesn't need local tweaking and retesting. When in the future Harbour will have internal UNICODE support, we will have to face the problem again, since we will need to support 4 types of conversion when interfacing Harbour HVM with Windows API (8bit-ANSI, 8bit-WIDE, UNICODE-ANSI, UNICODE-WIDE, plus the same in reverse direction). Which doesn't seem like making things simpler. I'm sorry if this is the end of the project for you, but I had preferred to see some real argument from your side, it's possible I'm missing something or my assumptions or general view of the topic is wrong, and in this case I'm happy to be corrected, so that at the end we make the best decision based on real facts and discussion. For sure you have something, if keeping non-UNICODE support is such important issue for you. All this has nothing to do with becoming Java and Python, it's only a technical detail which doesn't change much fundamental from usability or portability POV. [ BTW, unicows usage support could even be made simpler, or fully transparent, if needed, but it's already extremely simple, so I didn't even think about it. It was enough to spend quite a few days on the topic to actually making it as simple as it is now. ] Still awaiting for your actual arguments, as your time allows. Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
