[Prev][Next][Index][Thread]

# Re: [PROG] changing the value of player

- Date: Wed, 20 Sep 1995 17:14:20 PDT
- From:
- Cc: moo-cows@parc.xerox.com
- In-reply-to: ThwartedEfforts's message of "Wed, 20 Sep 1995 14:05:00 PDT" <m0svWKc-000JpnB@rci.ripco.com>

    ThwartedEfforts writes:
    > set_task_perms() isn't caring about the value of player.  It seems that when
    >  a call to a verb is made, the permissions of the calling verb are checked to
    >  see if wizardly, and if not, revert the value of player to what it was
    >  originally for the caller verb so it is not changed in the callee.
    > But I also have to ask the question: What was behind this implementation?

    Here's where it comes in handy that I didn't write the first version of MOO: I
    get to blame *some* of the bad design decisions on Stephen!  :-)

    Seriously, I never stumbled over this as a problem until just recently, in
    Jupiter code, and I didn't think of this issue when I reimplemented what
    Stephen had already done in his version.

    Anyway, the answer to your questions is `history', not `design'.  I'll think
    about simple ways to fix it, but I'm betting that it won't be trivial enough to
    be worth my while to do it, since the issue comes up so rarely and the
    workaround is so (relatively) painless.

    	Pavel

References:

- Re: [PROG] changing the value of player

- From: abakun@rci.ripco.com (ThwartedEfforts)

- Prev: Re: [PROG] changing the value of player
- Next: [Prog] Magic: The Moo.
- Index: MOO-cows
- Thread: MOO-cows

Home | Subject Index | Thread Index