In the relations language the

Entity(...) :
  defines Entity ...
  scopes Attribute
  scopes Role
  scopes Inverse
  scopes Shortcut

Attributes, Roles, Inverses and Shortcuts are different namespaces, because I need this when I do lookups. (Some language constructs only refer to roles for example.)

But I’d like to get ‘duplicate definition’-like errors when there attributes, rules, inverses or shortcuts defined with the same name in the same entity. How do I achieve that?

The same holds for C# where properties and fields live in the ‘same namespace’, but one needs distinguishing between the ‘2 namespaces’ when referring to them.

Submitted by Daco Harkes on 20 November 2014 at 11:04

Option 1: Use a single namespace, but assign different types to different kinds of definitions.
Option 2: Use different namespaces and constraints similar to the variable-hides-field-check in MiniJava.