[SVN] r4750 (OCaml)

William D. Neumann wneumann at cs.unm.edu
Tue Aug 15 16:22:43 UTC 2006

On Tue, 15 Aug 2006, Michael Sheets wrote:

> (Part of the global rename of entity.name.class to entity.name.type)
> • Rename entity.name.type.class.type to entity.name.class.class.type
> • Rename entity.name.class.type to entity.name.type.type, and yes that's intentional.
> • Rename entity.name.class.exception to entity.name.type.exception
> • Rename entity.name.class.variant to entity.name.type.variant
> • Change Symbol List exclusion preference to match above variant change.

I'm a bit confused here as to what the structure of these names is 
supposed to signify.  Mostly because we hove things like 
entity.name.class.class.type.ocaml refering to classes in OCaml, which are 
not types, yet this name has type in it.  This inclusion of type is more 
confusing when you consider that entity.name.class.type.ocaml also has 
type in the name, but only once, and this is actually a type.  So we 
should either have one more type in the class type name, or one less (and 
possibly one less class) in the name for classes.

Are the conventions for naming of entities anywhere online?  The manual 
only goes one level deep, and doesn't even mention entity.type....

William D. Neumann


"There's just so many extra children, we could just feed the
children to these tigers.  We don't need them, we're not doing 
anything with them.

Tigers are noble and sleek; children are loud and messy."

         -- Neko Case

Life is unfair.  Kill yourself or get over it.
 	-- Black Box Recorder

More information about the textmate-dev mailing list