Close, but not quite. The actual situation is that I placed the function
is_name() as an exact duplicate of stock CircleMUD's isname(), to avoid the
situation where a MUD administrator drops abbreviations code in without
contemplating the effects.
Now, I did *NOT* include the abbreviations in with the OLC+ package.
Rereading that passage brings one to the conclusion that the situation of
adding abbreviations is accounted for, and as long as you don't modify the
OLC+ function, you'll be fine.
At least the README was read. :)
-B.
Oh, and on another note, I'm thinking of releasing a new version of OLC+ (I
think I'll change the name though, as to not confuse people with the whole
Oasis != OLC+ situation). The main addition will be commandline OLC for
redit, medit, and oedit. I am not positive as of yet if I'll do it--school
is killing me.
At 10:36 AM 10/17/98 -0500, you wrote:
>> However, the OLC+.README says ...
>> (This uses the is_name function, a duplicate of isname()). The logic
>> is that it will search the list for the same name. DO NOT CHANGE
>> is_name() for ANY REASON, especially abbreviations code. This will
>> cause "Belga" to work as "Belgarath". A security hole.
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST