bug in function {metavariable}:name

[Guido.Bosch@loria.fr (Guido Bosch)]

In Centaur 1.2, the function {metavariable}:name returns/modifies  not
the name of a metavariable, but it's operator. This is not only
anoying, but also dangerous. 

Here is a script that shows you what I mean (I also verified with a
plain Centaur without VTP++ and object browser - it's the same behavior)
 

? meta
= #<Glider metavariable MODULE_NAME1>
? ;;; Describe object
#<Glider metavariable MODULE_NAME1> is a #:tree:Glider:meta
  name: fragment-Glider-meta
  operator: #<operator meta>
  sons: ((MODULE_NAME1 . 0) tree)
  father: #<Glider module_header>
= ()
? ({metavariable}:name meta)
= #<operator meta>
? (eq ({metavariable}:name meta) ({tree}:operator meta))
= t

;; this is was I really wanted to get or modify 
? (caar ({tree}:sons meta))
= MODULE_NAME1
? 


Could you send me a fix if there is one? 

	Guido