Thanks Chen, yes, it's DBCS OS issue, what I'm unsure of if it's a compiler issue or some more general stuff. Both ways, we should identity all similar spots in Harbour source (and the rule to avoid that in the future as well). This may also happen in generated .c code. It seems strange that a compiler parser should behave differently due to OS language, but maybe the OS text stream reader functions do some magic on the input and pass that to BCC. Impossible (for me) to tell without more tests.
Brgds, Viktor On Tue, Mar 17, 2009 at 9:04 AM, Chen Kedem <n...@synel.co.il> wrote: > Viktoer, > > > If this is a BCC problem, it may be one. > > Just tested rev10625, and all files in source/lang compiled with no problem > (like it was for quite long time). > > I'm using Borland C++Builder 5.0, WinNT 4 sp6a (Hebrew Enabled), > mingw32-make.exe 3.81 > > Maybe it is something with UNICODE or double-byes OS specific. > I'll try now with UNICODE build... > > Chen. > _______________________________________________ > Harbour mailing list > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour >
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
