Hi Przemek and all, Suppose there is a perfectly valid .prg file, but instead of TAB or SPACE chars for indenting, say we have Chr(160) chars (looks like space in my editor).
In this case Harbour will compile the source without a single error or warning, yet the resulting .c file will virtually contain no code. CA-Cl*pper would throw tons of "Illegal char" errors for the same .prg. I think Harbour should do something similar to save the time looking for a problem in a seemingly error-free source file. [ I'm experiencing this everytime I save a message from this list containing some code (as .rtf from OS X mail) and (using WordPad) I copy/paste the code to a .prg. ] Brgds, Viktor _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
