Hello Viktor, > Any opinions on this?
Sorry, but I don't agree with removing the non-UNICODE mode from Harbour source code. My working environment is Win98SE and it will create the additional difficulties for creating and managing of the Harbour compiler (for me and for clientes with Win9x). BTW There are the Windows applications in two builds - UNICODE and non-UNICODE. Thanks for attention! -- Kind Regards, Grigory Viktor Szakáts wrote: > > Hi All, > > If that simplifies things (which it definitely does), and > the majority of developers agree with it, we can drop > non-UNICODE mode altogether from Harbour source code. > > It's unlikely we shall ever support Windows 3.x or Win32s, > and unicows solution works just perfect now to cover Win9x/ME > host versions, so I can see no hard reason to maintain duplicate > code paths for both UNICODE and non-UNICODE Windows API > support. > > Having only UNICODE path could greatly simplify code in > many crucial points, making it easier to maintain, > extend, debug and keep bug free. Especially if we want > to move towards internal (HVM) unicode support in the > future. > > Any opinions on this? > > Viktor > > -- View this message in context: http://old.nabble.com/SF.net-SVN%3A-harbour-project%3A-14412--trunk-harbour-tp28398083p28400133.html Sent from the Harbour - Dev mailing list archive at Nabble.com. _______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
