Re: spurious names

Thanks, now fixed. Unsavoury introduction of new names
in the TC when processing class defns -- it introduced 
missing method bindings for class members by creating
names that were derived from the method name by simply
prefixing "default_". Quite bizarre, really.

--sigbjorn

----- Original Message ----- 
From: "Iavor S. Diatchki" <[email protected]>
To: "hugs-bugs" <[email protected]>
Sent: Tuesday, February 11, 2003 11:02
Subject: spurious names


> hello,
> 
> i run into the following problem:
> 
> class C t where
>    elem :: t
> 
> -- default_elem = 3
> 
> -- when default_elem is not used
> -- INTERNAL ERROR: pmcTerm
> 
> -- instance C Int where
> --   elem = default_elem
> 
> -- when default_elem is used
> -- INTERNAL ERROR: typeAp1
> 
> -- when default_elem is not defined (at command prompt)
> -- :i default_elem
> -- default_elem :: <unknown type>
> 
> 
> it looks like hugs introduces new (valid) names into the program.
> would it be possible to hide this from the user?
> 
> thanks
> iavor
> 
> -- 
> ==================================================
> | Iavor S. Diatchki, Ph.D. student               |
> | Department of Computer Science and Engineering |
> | School of OGI at OHSU                          |
> | http://www.cse.ogi.edu/~diatchki               |
> ==================================================
> 
> _______________________________________________
> Hugs-Bugs mailing list
> [email protected]
> http://www.haskell.org/mailman/listinfo/hugs-bugs