Panic due to commented backslash

[tiymat]

Describe the bug:
When a line is commented with #, if the line ends with a \ it will cause a nil pointer dereference.

Expected behaviour:
Nothing in the comment should affect execution.

Screenshots:

Platform (please complete the following information):

• OS, output from uname -a if supported: 6.12.10-arch1-1
• Terminal Emulator: kitty 0.39.0
• Murex version, output from version --no-app-name: 6.4.2063 (develop)

Additional context
tree.statement is nil in parse_comment.go in its invocation here

		case '\\':
			next := tree.nextChar()
			if next == '\r' || next == '\n' {
				tree.statement.ignoreCrLf = true
			}

		}

[lmorg]

Nice catch. You're right about tree.statement being nil

Escaping in comments was intended to be used as a way of documenting a command's parameters, eg

ls     # directory listing \
   -l  # include timestamps et al \
   -A  # include dot-prefixed files

...whereas in your example there isn't a command.

I think the logical action here might just be for the parser to ignore the escape character if there isn't a command.

If we make that assumption then the fix is very easy, just test if tree.statement is nil as part of the same line endings check. (fix incoming)

[tiymat]

Makes sense, thanks!