-
Notifications
You must be signed in to change notification settings - Fork 14
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
ic3: property numbers #9
Comments
I just made a simple assumption to keep going when I was working
on incorporating ic3. Matthias fixed the problem in one of PRs.
Eugene
…On Sun, May 21, 2017 at 11:13 AM, Daniel Kroening ***@***.***> wrote:
The 'short_name' idea seems to be that properties end on a dot followed by
a unique number. This is not the case.
Instead of --prop, please use --property, to be consistent with the rest
of ebmc.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#9>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AS5pClFBqDOx2tTzLZP9SXT4TjjoscG8ks5r8FSlgaJpZM4NhoNu>
.
|
I will replace --prop to --property.
Eugene
…On Sun, May 21, 2017 at 11:13 AM, Daniel Kroening ***@***.***> wrote:
Assigned #9 <#9> to @eigold
<https://github.com/eigold>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AS5pClFBqDOx2tTzLZP9SXT4TjjoscG8ks5r8FSlgaJpZM4NhoNu>
.
|
Okay, now I see what Daniel's comment is about. Option --property of ebmc actually assumes |
Daniel,
So instead of just giving the order number of a property, one has to use the Eugene |
I took a closer look and found out that the first part of the prefix specifies a module name rather Still, the word 'property' in a property name seems to be redundant :-) |
The 'short_name' idea seems to be that properties end on a dot followed by a unique number. This is not the case.
Instead of --prop, please use --property, to be consistent with the rest of ebmc.
The text was updated successfully, but these errors were encountered: