Issue293

Title improve handling of type name that clash with predicate names
Priority wish Status resolved
Superseder Nosy List florian, malte
Assigned To Keywords
Optional summary

Created on 2011-11-07.18:56:24 by malte, last changed by malte.

Messages
msg3237 (view) Author: malte Date: 2014-07-25.08:40:20
Yes, closing this one.
msg3236 (view) Author: florian Date: 2014-07-25.08:28:03
Duplicate of issue171?
msg2920 (view) Author: malte Date: 2014-02-04.11:06:59
See issue413 for a test case.
msg1881 (view) Author: malte Date: 2011-11-07.18:56:24
According to my reading of the PDDL 1 spec, it is not allowed to have a
predicate and a type that have the same name. (See msg1249.) Nevertheless, this
happens in the wild, and in those cases we should either

1) give a meaningful error message that specifically says that there is a
predicate/type name clash, or
2) support this -- possibly with a warning.

In the second case, one way to support this would be to
1. detect if a clash occurs, and if so
2. rename the type to "T@<original type>" or some such everywhere (i.e. in all
typed lists -- :constants and :objects definitions, parameter lists for
predicates and actions, and quantifiers including quantified effects)

The renaming (step 2.) should *only* happen if there is a clash, so that the
correct semantics (reusing types as predicates) is still supported.
History
Date User Action Args
2014-07-25 08:40:20maltesetstatus: chatting -> resolved
messages: + msg3237
2014-07-25 08:28:03floriansetnosy: + florian
messages: + msg3236
2014-02-04 11:06:59maltesetmessages: + msg2920
2011-11-07 18:56:24maltecreate