And a line is anything between a $crlf or a | and the next $crlf or |. it will comment everything on a "line" when used at the beginning of the "line". I think it's a much better idea to have your script use the the way it's meant to be handled. But I just don't think it's a good idea to start making things do different things in different situations. You would have the comment EVERYTHING on a line in one instance, but only specific things on a "line" in the other instance. If a change was made, then the would act differently in different instances and that's rarely a good idea in a programming/scripting language. There is no special coding for it when it's in the middle of a line. It is treating it just like it is always treated when at the beginning of a line. Right now, it looks like mIRC is not doing anything special with the. If you were to write the code like this (without |'s), you would expect the to comment out everything on the line including the }.
#MIRC REGISTRATION CODE 7.43 FULL#
There might be mid-line commenting in some languages in the form of /* */, but that has an END, whereas does not.Īs you can see here, also comments the full "line" of code, which includes a. There's end-line commenting in some languages. I'm trying to think of other languages with mid-line commenting and can't come up with any off the top of my head. Otherwise, you're going to have to treat mid-line 's differently than beginning-line 's because you'd have to tell mid-line 's to NOT comment a }. With |'s, the entire line is what is between one | and the next (or the end of the line). I'm not really sure if that should be changed. If you were to put a | before the final bracket on that line, it would probably work as you are wanting. However, your last example, the would comment not just noop, but also the end bracket, which of course messes up the code. As such, after a | works as a comment for that specific command. I'm sure mIRC is looking at that and treating the |'s like they are meant to be.
0 kommentar(er)
