Wrong syntax highlighting for q comments

[010100111001]

1. Forward slash for opening block comment must be first and only character on a single line.
2. Back slash for closing block comment must be first and only character on a single line.
3. Inline comments must be preceded by closing square brackets or closing bracket or space.

[010100111001]

My JSON for comments only looks like:
{
"name": "comment.block.source.q",
"begin": "^/[ ]$",
"end" : "^\[ ]$",
"comment": "string"
},
{
"name": "comment.block.source.q",
"match": "^/.+",
"comment": "string"
},
{
"name": "comment.line.source.q",
"match": " /.*",
"comment": "string"
},

[kimtang]

Looks good. Thanks for your contribution.
Let me test it on my machine and I will push this into github.

[010100111001]

There is still one comment highlighting that I have left out since my solution is not elegant. "" by itself on a single line will make the interpreter to ignore the rest of the q script.

Since I couldn't find a regex for EOF, I used a work-around (WAR):
{
"name": "comment.block.source.q",
"begin": "^\\$",
"end" : "<>",
"comment": "string"
},

The WAR does not work if someone does have the text "<>" string after a single line "" in their source

[bravegag]

I'm not sure if I have the same problem because the issue description is not very clear but syntax highlighting for comments doesn't work unless the comment is at the beginning of the line e.g. if I use any identation due to e.g. functions then my comments are not syntax highlighted correctly e.g.

/- this is hightlighted correctly
________ /- this is NOThightlighted correctly
________ / this is hightlighted correctly
________ /this is NOThightlighted correctly

where ________ is whatever spacing, tabs