-
Notifications
You must be signed in to change notification settings - Fork 20
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
Minor mistake in section 3.5.2 #1
Comments
Yes, you are right. We will fix this. Thanks a lot! |
You are welcome. Another very minor thing: Under Listing 3.23, it reads: "The loop invariant not_foundis ... ". It needs a space between 'not_found' and 'is'. I plan to go through the whole book but it will take me a while because I can only do it in my spare time. If the source code of the pdf is in latex and you make it available, I could submit patches if I run into anything else. |
Again thanks a lot. I fixed it in our development version. We will provide a new release soon. I hope it doesn't bother your that we do not put the latex source on GitHub... |
Regarding "EqualRanges": This problem occurred because we had a command "\equalrange" that expands to something like "equal_range" and a command "\equalranges" that expanded to "EqualRanges". |
No worries. If you guys don't want to publish the latex source, that's fine. This is a great book and a great introduction to ACSL. The first time I tried Frama-C/ACSL was many years ago and I did not get very far. I think it will be a lot easier this time around because I can use your book as a reference. Thank you guys at Fraunhofer for putting it together. |
Thank you for your nice comments. If you have time I would like to know more about your interest in Frama-C/ACSL. Perhaps, it's better when you write me an email: jens.gerlach@fokus.fraunhofer.de |
I see that the problem was fixed in 15.1.2. Therefore, I am closing this issue. Cheers |
In section 3.5.2 (Formal specification of equal and mismatch), the first sentence reads: "Using predicate equal_range we can formulate the specification of equal..." . Given that EqualRanges (and not equal_range) was the predicate defined just above this section, I believe you meant: "Using predicate EqualRanges ...".
BTW: I was going to submit a patch but I did not find the files that are used to generate the pdf. This is the reason why I did not submit a patch.
The text was updated successfully, but these errors were encountered: