Found a problem with Vex's optimizer

[Tal'Rarity]

Apparently tooltips get erased if you use the ctrl + enter trick, its better just to use |n if anyone wanted a fix for this since the proper linebreak still works even though it looks messier as well takes 2 char's, at least the optimizer accepts it.

Does anyone know how to fix the ctrl + enter linebreak for this tool? Considering its the best optimizer for wc3 in wc3 history, wonder if Vex still checks?

 

[PurgeandFire]

He might still check his email, but probably not much else. It is closed source unless someone emails him for the source, so not much we can do. Thanks for the bug report though, it might be useful to know in the future.

You can always post in the wc3c thread on the off-chance that he'll update it.

 

[Dr Super Good]

Disable string inlining? The problem is likely because if it inlines an external string into the JASS script it has to strip it of all line breaks as they would cause syntax errors since line breaks are part of the JASS syntax.

 

[Zwiebelchen]

since line breaks are part of the JASS syntax.

I always wondered why they did that in a verbose language. I mean; every line starts with a keyword anyway; what's the point in having line-breaks part of the syntax?

 

[Dr Super Good]

what's the point in having line-breaks part of the syntax?

Can make parsing easier I imagine. Instead of passing a stream of characters, you can pass a stream of lines. Even with keywords at the start of every line, it saves you from testing for key words at every stage of parsing.

Languages like python depend heavily on it because they have no block open/close syntax. Hence new lines and indentation are the only way to define blocks.

SC2's Galaxy has no problem being written to a single massive continuous line. However I do not think multi-line strings are permitted hence \n is needed.