Your argument makes no sense. There's always been multiple ways to do
many things in pascal, and it's never caused any more confusion than any
other typical language construct.
Take for instance, comments.
{ this is a comment}
works just as well as
(* this is a comment *)
I don't believe I've ever seen you complain about multiple ways to put
comments in the code
Would that also cause the same issues as you argue for the multiple line
string support?
I'd guess not at all.
Why?
Because some folks use one, and some use the other, functionally they're
the same. Whether one takes more processing than the other isn't
something I've bothered to check, but honestly, who cares? Both
accomplish the same thing, and folks can use whichever one they like.
I find your arguing about multiline strings to be exactly the same thing.
Who cares?
Use it or don't, it makes no difference to anyone except the programmers
that don't like it for whatever obscure reason, but it affects nothing
as far as the language is concerned, so why get so worked about it?
I see no confusion here, nor do I agree that it can/will lead to
problems you describe, and if it does, then someone can simply use
search and replace to solve the problem.
_______________________________________________
fpc-pascal maillist - fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
