Anyway, I've been working on some code that "requires" an expression to be inside a continuation section. Really I could go another route but it would be much easier this way. I've included my test script at the bottom. Now the documentation says that a closing parenthesis in the CS options will allow expressions, but I can't get it to work and "just me" says that it is not an option either (see below). So, I would just like some clarification on this issue. If it's not supported, the offending lines should probably be removed to prevent further confusion. I would imagine that the Devs are busy, but his post is from almost a year ago.
Also, in testing this out I found that the documentation says that adding "Com" to the CS options will allow semi-colon comments but not block ones. In my testing, the opposite is true. Semi-colon comments are removed and blocks are allowed. Is this the way it should be?just me wrote:Never noticed it and had to read the docs more than once:It's not an option of a continuation section, though mentioned there.) [v1.1.01+]: If a closing parenthesis appears in the continuation section's options (except as a parameter of the Join option), the line is reinterpreted as an expression instead of the beginning of a continuation section. This allows expressions like (x.y)[z]() to work without the need to escape the opening parenthesis.
Thank you for your time.Comments (or Comment or Com or C) [v1.0.45.03+]: Allows semicolon comments inside the continuation section (but not /*..*/). Such comments (along with any spaces and tabs to their left) are entirely omitted from the joined result rather than being treated as literal text. Each comment can appear to the right of a line or on a new line by itself.
Code: Select all
test =
( LTrim Com ; ")" commented out because the script errors out
asdfasldkf
/*testing*/
/**/ ;test
; testing
asdfalsdfkasdf`n
tes(3)
asdfasd
f
)
msgbox, % test
exitapp
tes(x)
{
Return, x+2
}