Skip to content
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

Properly report errors when converting integers #104

Closed
GiovanniBussi opened this issue Jun 25, 2014 · 1 comment
Closed

Properly report errors when converting integers #104

GiovanniBussi opened this issue Jun 25, 2014 · 1 comment
Assignees

Comments

@GiovanniBussi
Copy link
Member

The code is not behaving consistently when users do mistakes in the input such as passing a real instead of an integer. Plumed should just give an error in these cases.
See https://groups.google.com/d/msg/plumed-users/JTbvhtXQRx0/i95P189HXIYJ

@GiovanniBussi GiovanniBussi added this to the Stable release (2.0) milestone Jun 25, 2014
@GiovanniBussi GiovanniBussi self-assigned this Jun 25, 2014
@GiovanniBussi
Copy link
Member Author

I had a quick look it seems not trivial. The difficulty is that we are using the same return value ("false") to detect when a number is missing and when it is wrong. I remove any milestone (probably it is better to change this in the master branch later)

@GiovanniBussi GiovanniBussi removed this from the Stable release (2.0) milestone Jun 25, 2014
@GiovanniBussi GiovanniBussi added this to the Version 2.2 milestone Jul 4, 2014
@GiovanniBussi GiovanniBussi removed this from the Version 2.2 milestone Jun 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant