Yes, but then we got two different types of fruit flies.
This means absolutely nothing and proves no point to speak of, so... ok?
Sorry for getting a bit frustrated, but I quite frankly find the level of continued opposition to the
entire concept of multi-line strings, despite the fact that I've gone
way out of my way to address all of the reasonable concerns with them that I could, to be utterly mind-boggling.
It is an
incredibly simplistic piece of functionality to add to the language (or more specifically, to add to FPC's implementation of the language) that is
not going to have any negative impact whatsoever on anyone's existing workflow.
Some of the comments in this thread are
far too uncannily similar to the ridiculous non-arguments I often hear from backwards-thinking Golang users about how generics are somehow guaranteed to "ruin Go" if ever added to it, for my tastes. (Ironically Go
does however have multiline strings, BTW!)