Hi Przemek,
[ 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. ]
You will still have this problem. Only error message
will be generated during compilation. I understand that
That alone would have saved me a few hours already :)
Which would be the point basically.
it may help you to clean the source code but it will
also forbid using national characters in some constructions
just like in Clipper. In few cases it will be valid code,
f.e. Clipper cannot preprocess this code and generates
error messages:
#command OUT <*x*> => qout( #<x> )
OUT BŁĄD
I do not have any special preferences here. It should be
group decision if we want to keep in PP support for national
characters or not.
I see, and thanks for the explanation.
Do you think this logic could be moved to the compiler (rather
than the PP), to avoid these drawbacks? I understand
preprocessed Clipper/Harbour code normally cannot have any
non-ASCII chars, except inside string delimiters (plus maybe
some other special, but well defined places).
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
