Re: @create (continued)

• Date: Thu, 10 Oct 1996 07:09:21 PDT
• From:
  <thomas@xs4all.nl>
• cc: moo-cows@parc.xerox.com
• Content-Type: TEXT/PLAIN; charset=US-ASCII
• In-Reply-To: <Pine.3.89.9610091729.A10179-0100000@chico.idt-isep.ipp.pt>

On Wed, 9 Oct 1996, Sergio Costa wrote:

>   I get this when i start the moo process.. :
> Oct  9 17:06:35: VALIDATING the object hierarchies ... finished.
> Oct  9 17:06:35: LOADING: Reading 1626 MOO verb programs...
> Oct  9 17:06:36: PARSER: Warning in #20:explode:
> Oct  9 17:06:36:            Line 5:  Renaming old use of new keyword: break
> Oct  9 17:06:38: PARSER: Warning in #56:parse_templist_duration:
> Oct  9 17:06:38:            Line 4:  Renaming old use of new keyword: try
> Oct  9 17:06:38: PARSER: Warning in #58:get_prep:
> Oct  9 17:06:38:            Line 9:  Renaming old use of new keyword: try
> Oct  9 17:06:38: PARSER: Warning in #75:check_cache:
> Oct  9 17:06:38:            Line 15:  Renaming old use of new keyword: break
> Oct  9 17:06:39: LOADING: Done reading 1626 verb programs...

>   I am running LambdaMOO-latest with LambdaCore-latest in a alpha 
> processor running OSF/1

The transition from 1.7.9 to 1.8.0 introduced some new keywords, 'try' and
'break' among others. In the pervious servers you could have 'try' and
'break' as variables in your verbs, in the new server you cannot. Therefor,
the server changes any appearance of such a variable to a harmless one (with
a _ in front i think) 

Of course, it only does this when it's converting an old style DB to the new
style, and therefor only does this once (it dumps it in the new style)

Regards,
Thomas.

• @create (continued)
• From: Sergio Costa <i940537@chico.idt-isep.ipp.pt>

• Prev: RE: @create (continued)
• Next: @program is not working
• Index: MOO-cows
• Thread: MOO-cows