[983] in Coldmud discussion meeting

Re: [COLD] 'user()' builtin function..

daemon@ATHENA.MIT.EDU (Fri Apr 26 08:07:36 1996 )

Date: Fri, 26 Apr 1996 04:41:31 -0700 (PDT)
From: No one of any consequence <seanl@beef.bovine.com>
To: Brandon Gillespie <brandon@tombstone.sunrem.com>
cc: coldstuff@cold.org
In-Reply-To: <Pine.BSF.3.91.960425225006.10344A-100000@tombstone.sunrem.com>

I vote for user(), because it's short, and I'm lazy.

-Sean

On Thu, 25 Apr 1996, Brandon Gillespie wrote:

> On Wed, 24 Apr 1996, Dancer wrote:
> > > Okay, I agree with Quinn, 'issuer' sounds more generic, if not, I vote 
> > > for 'controller'.
> > 
> > If you want generic, try 'initiator()'. Personally, I'd really like
> > something like that. There are quite a lot of times when I'd like to pin
> > down where  .tell() came from (usually from a room announce, from some
> > code on a user, started by...who? Being able to get the dbref of the
> > enactor would be a BIG help).
> 
> Ok, from discussions here and numerous online I'm personally narrowing it 
> down to one of:
> 
>       origin()
>       user()
> 
> Both of which work.  The primary bonus of 'user()' is it is short, and
> should be easy to pickup by most beginning users--but it is not as
> appropriate in more proffesional applications (however, it is also not
> absolutely inappropriate either).  The drawback to 'origin()' is that it
> doesn't imply you can change it (of course, it doesn't imply you can't
> either.. ;) I'm going to be making these changes soon, of these two which
> do people prefer? 
> 
> -Brandon
>