I've worked for a very large company where use of the ternary operator was banned as it is not at all readable and had actually been identified as a regular source of bugs.
I suspect there's no justification for a tab concatenation operator. I do quite like ':' as a newline concatenation shorthand.
However, in all of this I think Bjornke has hit the nail on the head:
To get rid of text formatting issues in scripts, I'd rater have an easy way to never enter user-read text within the script... great way to be ready for localisation too!
Built-in localisable string references and a localisation system would be really useful. Qt does this a nice way, where you have a tr() macro around a user readable string - if the string doesn't have a corresponding localisation for the current language then the string itself is used - the macro doubles up as a marker for tools that process the source and manage lists of all the localisable strings and translations. I bet we could come up with an even nicer syntax/marker for doing the same thing in LiveCode.
Code: Select all
set the escapedStrings to true
put "This\nhas\nmany\nlines\nin\nit" into tVar
I like it. This might be handy if you want to use LiveCode to process ascii representations of escaped string output/input for other programs or externals. Could be useful for implementing the tools to handle localisation.