-
Notifications
You must be signed in to change notification settings - Fork 119
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
64-bit compatibility issue in muParserBase.h #62
Comments
Should be -1 but it not really dangerous since strind::npos is defined to be -1. No truncation taking place. |
I see what you mean, agreed. But MSVC does complain about truncation; the warning itself should be enough reason to fix this piece of code, IMO, regardless of how justified the warning is. |
@beltoforion could you register the project on appveyor to enable msvc builds so we can actually see what's going on ? (https://www.appveyor.com/) The appveyor configuration was added in #38 but not actually used. If you want I can set it up for you if you grant me the rights to the repository. |
I registered the project in my account, but there is no automatic trigger. |
Sorry, I have no idea what appveyyor is or does. Never used it before. |
Great, I could enable Appveyor, see the new README.rst. |
@VioletGiraffe what of msvc version did you use ? any special flags ? |
@jschueller: msvc 2017 (v141 toolset), |
@jschueller: giving admin rights does not seem to be so easy. Seems i need to create a new organization and transfer project ownership. (Something i would do if everything else fails) I connected muparser to travis-ci can you access it there? |
Travis works properly, thanks. |
I added it to appveyor. Please check out if you see it. |
std::string::npos
issize_type
, it's a 64-bit value in 64-bit mode. The highlighted line truncates it to 32-bit signedint
. It's probably not causing any actual runtime errors, but looks bad and causes a host of compiler warnings (remember, it's in .h file so a warning is emitted for every .cpp that includes it).The text was updated successfully, but these errors were encountered: