Zugg Software :: View topic - [1.30] // comments tricking the parser

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

#TRIGGER {pattern} {// comment}

errors with 'unmatched braces'
It's fixed by putting the closing bracket on the following line, but CMUD is taking the closing } as part of the comment

Posted: Tue May 01, 2007 12:24 am

That is because the // command marks everything until the end of the line as a comment. So, the } is part of the comment. This is how // works in all other languages. If you want to use //, then you need to use the multiline syntax and not the single line syntax. There is no way to fix this.

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

It was only because CMUD exports it in this format that I flagged it, so an export then reimport will fail

Posted: Tue May 01, 2007 1:56 am

Ahh, well, that would be the bug then. I'll add the export bug to the bug list. However, this should only occur when your trigger is empty (except for the comment).

Edited: Actually, I can't reproduce this. Exporting it should produce XML which should import correctly. Exactly how are you exporting/importing it? Can you post the XML file that is produced?

Only the Reformat command should cause this problem. If you have:

Wizard Joined: 03 Mar 2001 Posts: 1127 Location: London

Hmm, it was an export from a while ago. I'll try again from the clean 1.30 install I did yesterday and post again if it fails.