 |
The Raven
Magician
Joined: 13 Oct 2000
Posts: 463
|
 Posted: Fri Nov 17, 2006 1:56 am
Disallow Pipe for separating Classes
|
Since your syntax is all set for / characters, you should disallow the | character in separating classes. It'd also be spiffy if the section of the parser that determines what class is being referred to saw | and warned the user they are illegal.
I've been using pipes all this time, and it was only when I researched how to refer to other modules that I found your post describing the //Module/Class/Path syntax. Pipes don't work there, though they do if you're referring to a Class|In|The|Current|Module. It's possible many of my scripting problems have been related to bugs using pipes. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Mon Nov 20, 2006 3:20 pm
|
The pipes are allowed when importing zMUD settings, and in the ClassName argument of some commands (like #ALIAS, etc). So, these are not actually handled by the "parser". They are handled by each individual command that parses their ClassName argument. But I'll look into this and see what I can do.
Unfortunately, the Compatibility Report is a simple set of regular expression tests...it doesn't actually understand the full parser syntax, so it would be hard to flag this without flagging most any other string list in your scripts. |
|
|
|
|
The Raven
Magician
Joined: 13 Oct 2000
Posts: 463
|
Posted: Mon Nov 20, 2006 5:18 pm
|
Perhaps pipes in classpaths could be enabled only when the 'compatibility mode' checkbox is on?
|
|
|
|
|
|
|
|
