Subject: Callers()

From: Byron Montgomerie <[email-masked]>
Date: Wed, 29 Sep 1993 14:24:19 -0700

The main use I see out of callers is to see what the name of the first verb was
or the last verb, would it be a good idea to include in the server builtin
variables something like first_caller and last_caller with values equal to the
first and last entries in callers()?

ie. callers()[length(callers())][2] can become first_caller[2];
    callers()[1][2] can become last_caller[2];

The benefit of this would be more readily understood code. Drawbacks 
include existing variables with the name last_caller or first_caller that would
have to be renamed.

Byron...
 __________________________________________________________________________
| __  ///    "Byron Montgomerie"  Internet: [email-masked]   __  /// |
| \\\///      "Does anybody here remember Vera Lynn?               \\\///  |
|  \XX/        How she said that we would meet again,               \XX/   |
|  Amiga       some sunny day..." -- Pink Floyd --                 Amiga   |
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

---

From: Pavel Curtis <[email-masked]>
Date: Wed, 29 Sep 1993 17:31:30 -0700

> Date:	Wed, 29 Sep 1993 14:24:19 -0700
> From:	Byron Montgomerie <[email-masked]>
> 
> The main use I see out of callers is to see what the name of the first verb
> was or the last verb, would it be a good idea to include in the server
> builtin variables something like first_caller and last_caller with values
> equal to the first and last entries in callers()?

I'm not at all convinced that this is a sufficiently common usage to justify
the addition of new built-in variables.  In fact, I'm not convinced that there
are *any* sufficiently common usages for this; I wouldn't mind cutting down on
the number of these variables, since they're really kind of gross from a
language design standpoint.

	Pavel