Forums Bug Reports Comments Bug?

I'm not for sure if this is a bug or not, but recently when testing things out. I sometimes make comments of old codes to make sure I don't messs the code up when editing.

I noticed it you have:

It says there is a bracket mismatch. But obviously there isn't.
Though if you have:



It works normally.
Am I just not doing something right, or is this an bug? .-.

/* and */ are meant to be at the start of the line.

See this.

Well, reading it, the parser thing should instead of jumping to the next line trying to find */ should read for the */ ;(

It seems pretty intentional behaviour and so beyond the realms of a bug. IMO this is more of a Feature Suggestion, but I can see how it might be taken as a bug I suppose...

Either way I'd like to see this changed.

mIRC uses unquoted strings, so if you had a peice of text that contained */ in it and you tried to enclose it in a multi-line comment it could create major bugs by ending the comment prematurely without the scripter knowing.

In short, changing this behaviour would be a very big mistake.

If it only interpreted */ as an end of the comment if a comment was already started with /* then there would be no problem (or atleast, not a very big one).

I can see problems with regex if you wanted to put a regex code into a comment like that.

Much easier to put multi-line comments or else use a semicolon.



Anything wrong with just doing that?

Only if the regex wants to match 0 or more forward slashes, which isn't particularly likely but ok...

My support is dropped, however, since I just noticed this works fine, without the need to put */ on a new line...

/* moo
*/ moo

So there's really no need to change it.