Re: Wish list

• Date: Tue, 29 Aug 1995 07:13:13 PDT
• From:
  sir@po.cwru.edu (Seth I. Rich)
• Reply-to:
  sir@po.cwru.edu (Seth I. Rich)

> Still, I might like to do something like
>   @prop me.office $office
> which returns
>   Syntax error in initial value:  `$' unexpected
> This is a product of @prop, and I could hack that but I don't want to
> have to hack every @-verb that I might want to give an expression
> argument to.  I'm not sure if a server mod is the optimal solution, but
> hacking oodles of core programmer verbs doesn't strike me as optimal
> either.

The goal is -not- to have the server do complex parsing.  I've found it
irritating that the server doesn't know the properties directly defined
on #0 so I can refer to them in commands, but the solution is to do the
object-matching in-DB.  (Recall that not every Core defines its objects
as offshoots of #0; that's a LambdaCore thing.)

Take an example I'm trying to recall from earlier:
  @prop #126.foo #125.bar
... where the writer wished the server to somehow know to leave
'#126.foo' as a string to be used later in add_propert() but also to
know to turn '#125.bar' into a value.  This gets into having the server
support more than I'd like -- IMO the verb doing the executing should
look at '#125.bar' and do whatever it wants/ought to the string typed 
by the user.

Seth / Blackbriar

--
----------------------------------------------------------------------
Seth I. Rich
Woo, woo!  OpalMOO's back!       There is nothing more precious than
Rabbits on walls, no problem.    a tear of true repentance.

• Re: Wish list
• From: Coolin MacKaarmick <colin@tripod.tripod.com>

• Prev: Re: Wish list
• Next: Re: Wish list
• Index: MOO-cows
• Thread: MOO-cows