i not sure what this feature making pascal better and easier. at least coz many people uses editors which cut trailing spaces which can be part of these multiline strings.
Think about it this way: the reason that so many editors remove trailing whitespace automatically is because pretty much nobody ever specifically
wants trailing whitespace. It's something that most of the time just winds up as a part of the line accidentally, and that serves no purpose I can think of in the vast majority of cases other than to unnecessarily increase the file size of the document in question.
Also, to be clear, as I've said in earlier comments, as far as my implementation of multi-line strings for FPC goes the presence or non-presence of trailing whitespace does not affect them in any way you could physically notice unless you were actively checking to see if it was there.
And am already testing testing this feature using Lazarus and it works quite nice. And yes there are some hiccups like if I write word "type" inside new construction Lazarus will protest that type can't be there. But still it is not reason to not implement this feature.
Glad you like it! As far as the "type" thing: yes, that would be due to Lazarus "CodeTools" (which is separate from SynEdit, to be clear) not currently being aware of multi-line strings. I'm quite willing to (and probably will) work up a patch for it myself, but I don't see much point in spending a lot of time on it until the actual language feature is merged to FPC trunk.