[1206] in Coldmud discussion meeting

Re: [COLD] cold stuff ;)

daemon@ATHENA.MIT.EDU (Thu Jan 2 17:12:30 1997 )

Date: Thu, 02 Jan 1997 14:09:08 -0800
To: Brandon Gillespie <brandon@cold.org>
From: Jeff Kesselman <jeffk@ten.net>
Cc: coldstuff@cold.org

At 02:44 PM 1/2/97 -0700, you wrote:

>
>caller/sender/definer etc are not related to user()  They are task/frame
>functions.  user() is not--it is simply a mechanism that MAY be used to

My point precisely, except I'm saying it SHOULD be a task/frame function.

>>  I'm not
>really seeing what the problem is, when all you have to do is put a call
>to set_user() as the first operation in $connection.parse(). 

yes this works, i just don't think its terribly clean is all and, to be
honest,  though it IS useful, it would probably be MORE appropriate to do
such data storage and retrieval in-db, not as part of the language...

However I DO see a use for a function that queries into the data the system
already has on the call chain...

> Also, the
>system now works well with heartbeat and the like.  Should $sys be
>returned as the user() when a task was called from a heartbeat?  

ABSOLUTELY it should return $sys as %$sys is the topmost object on the call
stack.

Lets forget about user() though for simplicity and i will merely say that I
want a top() function that returns the topmost object on the call stack in
a maximally efficient manner.  The fact that I thought this was what user()
was going to be is somewhat irrelevant.

JK