Fixed variadic function calls with named values for required parameters.
v1.1.13.01
Fixed scripts which begin with a parenthesized expression like (expr).
Revised handling of named actions for consistency and to fix bugs.

User-defined commands are now handled the same as built-in commands,
in that ternary and post-inc/dec no longer take priority (cmd ?x:y).
msgobx,() was treated as an expression instead of an error.
msgobx,[] as above.
n,++ was treated as an expression (which silently failed).
fun () was treated as an expression instead of a user-defined command.
Changed URL.
Fixed `x & y::` to fire both `x::` and `x up::` when x is released.
Fixed ImageSearch to set ErrorLevel=2, not 0, when a GDI call fails.
Fixed EnvGet crashing the program when the var exceeds 32767 chars.
Fixed a minor error-handling bug.

Specifically, StatusBarWait may have thrown an exception with an
incorrect ErrorLevel value (1 instead of 2) when in a Try block.
Merge branch 'master' into alpha
Revised command error-handling.

- Commands generally use ErrorLevel to report failure, and sometimes
  throw an exception (e.g. for invalid parameters).  Wrapping commands
  in a TRY block no longer affects this behaviour.
- Commands which set ErrorLevel and don't have exactly one output var
  (which would be used as a return value) now return !ErrorLevel when
  called with function syntax (true on success, false on failure).
  Excludes RunWait() and SendMessage(), which return ErrorLevel.
- Commands which set ErrorLevel now do so regardless of which syntax is
  used to call them.
- All WinSet' functions now return 1 on success, 0 on failure,
  while ErrorLevel is set to 0 on success, 1 on failure.
- WinSetAlwaysOnTop throws an error when the parameter is invalid.
- FileRecycle and FileGetVersion throw an error when filename is blank.
- ControlFocus now sets ErrorLevel when SetFocus fails.
- DllCall now throws exceptions instead of setting ErrorLevel.
- RegEx functions now throw an exception if there is a compile error.
First pass at implementing FINALLY, see details:

- FINALLY block allows for writing cleanup code that always runs:
  try { ... } finally { cleanupCode() }
  In this case (and unlike standalone TRY with no CATCH or FINALLY),
  the exception is NOT caught and after executing the FINALLY block,
  a CATCH block is still searched for upwards in the call stack.
- FINALLY block can also be used with CATCH:
  try { ... } catch var { ... } finally { cleanupCode() }
- goto and break/continue are blocked from exiting a try..finally block.
Remove goto/break/continue check inside finally blocks
Revised error-handling for expressions and objects.

Throw an exception under any of the following conditions:
- Failure to allocate memory for built-in function result.
- Stack underflow (typically caused by a syntax error).
- A dynamic function call or method call fails.
- x[y,z] fails due to x[y] containing a non-object value.
- An invocation fails because the target is not an object, or the
  method/property is not handled (excludes GET for associative arrays).
- An object-assignment fails due to memory allocation failure.

Allow ,) and ,]
finally block: Refactor code flow to fix ONLY_ONE_LINE mode bug
Fix load-time finally { ... } block validation
Add load time validation of jumps not exiting FINALLY blocks
Fixed a cause of heap corruption with FileRead *c on ANSI builds.
Fixed passing of local vars in recursive calls to variadic functions.
Merge pull request #26 from fincs/AutoHotkey_L