GPI wrote:
Ok, i what about this, when a string is startet with " the addition marks will work:
( \n = chr(13)+Chr(10) ? )
Yes, that would be fine. But I don't know, how hard it would be to implement this behaviour in the existing PB Parser. Fred?
Another Idea:
Another Compiler Directive switching between the old way of handling strings and the new one (opt-in of course so older code is not touched by this).
Could be called: EscapeCharsOn and EscapeCharsOff or something like this. This would produce cleaner looking Source Code.
What's wrong with having a setting to enable or disable support for escape sequences in strings (double AND single quoted strings)? I posted this suggestion ealier but didn't see anyone comment on it... So I will assume that it is simply the *best* way to accomplish escape sequences, until someone shows me otherwise!
This way Fred could even implement the support for escape sequences over time without having to change exising code. And if it was an option that could be enabled/disabled, he could even request beta testers who simply enable escape sequences and write their code...