=@ accessible by procedural attachment calls from
constraint for
The built-in =@ predicate (extensional identity check) is non-monotonic, so its use should be avoided in constraints attached to types.
atom a_/1 is ground in declaration of
One of the appropriate features of has a value restriction that is a ground a_/1 atom. Every feature structure of type will have the same value at this feature.
homomorphism condition fails for in and
It is not the case that the appropriateness restriction on the type is the unification of the appropriateness restrictions on and .
lexical description for is unsatisfiable
Incompatibilities in the lexical description for word could not produce a satisfying feature structure.
no chain rules found
All the grammar rules in the program were non-chain rules (no semantic heads).
no definite clauses found
There were no definite clause rules specified in the program.
no features introduced
There are no appropriate features for any types.
no functional descriptions found
There are no functional description definitions in the program.
no lexical rules found
There were no lexical rules specified in the program.
no lexicon found
There were no lexical entries specified in the program.
no non_chain rules found
All the grammar rules in the program were chain rules (with semantic heads).
no definite clause found
A definition for definite clause predicate , which was declared as the semantics predicate, was not found in the program.
no phrase structure rules found
There were no phrase structure rules specified in the program.
no semantics specification found
There was no specification of the semantics definite clause predicate in the program.
no types defined
There were no sub or intro declarations found in the program.
unary branch from to
The only subtype of is . In this situation, it is usually more efficient to elimate if every instance of is a .