-
Notifications
You must be signed in to change notification settings - Fork 4
GeFaqConfusingTypo
EricZinda edited this page Jun 30, 2023
·
3 revisions
I have a type/lexical entry/rule which doesn't seem to be inheriting a constraint from its supertype. What might be going on?
There are probably several possible causes for this, but here's one to look out for:
If you have a typo in a feature name at the very highest level of the feature structure (e.g., SYSNEM instead of SYNSEM in a lexical type), the LKB will simply posit a new feature. Any constraints written below that feature will be ineffective, since nothing else in the grammar is looking for SYSNEM. If you're particularly unlucky, the new feature will be ordered first, and you'll see what you're expecting to see when you do View > Type. You'd only notice that there's also a feature SYNSEM (inherited from a supetype, with lots of constraints associated with it) if you scroll down in the type window.
Home | Forum | Discussions | Events