-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
?after is not an accepted variable name #48
Comments
Thanks for this observation - you are right that "after" has been adopted as a keyword in the language, but unofficially, and it really should not prevent the use in this context. I will fix it. |
This one should be fixed, now. |
Hi @DerekLong101 and all, we just tested this because we wanted to update the Fast Downward build instructions to use a more recent version of VAL. We still observe the issue, also when building from scratch from the tip. |
It's true, "after" is a keyword in the PDDL dialect VAL supports. I need to take a look at the parser, I guess, to see whether I can easily avoid the lexer returning a token when the context wants a string.
Cheers
Derek
…________________________________
From: Gabi Roeger ***@***.***>
Sent: 10 October 2023 10:27
To: KCL-Planning/VAL ***@***.***>
Cc: Derek Long ***@***.***>; Mention ***@***.***>
Subject: Re: [KCL-Planning/VAL] ?after is not an accepted variable name (#48)
Hi @DerekLong101<https://github.com/DerekLong101> and all,
we just tested this because we wanted to update the Fast Downward build instructions to use a more recent version of VAL. We still observe the issue, also when building from scratch from the tip.
—
Reply to this email directly, view it on GitHub<#48 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AB2KOVBKPEH2GM7A6B3DOKTX6UIIXAVCNFSM4O52RPV2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCNZVGQ4DAOBSHEYA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
The domain data-network from last IPC (IPC 2018) is rejected with "Problem in domain definition". After lots of debugging, I figured out that the problem is that ?after seems not to be a valid variable name. I can only assume that "after" has a special meaning in other contexts, but nevertheless, this domain file should be accepted as valid PDDL in my opinion.
data-network-domain.tar.gz
The text was updated successfully, but these errors were encountered: