Skip to content

Conversation

@CodeShark
Copy link
Contributor

Explicit typecast to remove compiler warning.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is obviously the smaller change, but, couldn't nLastBlockFile just be unsigned?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it could - but that would require having to check whether that breaks anything...and if we're going down that route, we could also start changing a bunch of other variables...and I don't think I want to go down that path right now :)

@laanwj
Copy link
Member

laanwj commented Nov 16, 2015

ACK. I don't think nLastBlockFile can be usefully negative, but this is clearly the least risky change.

@paveljanik
Copy link
Contributor

ACK

The warning comes from #6948.

@gmaxwell
Copy link
Contributor

ACK.

@gmaxwell gmaxwell merged commit 4d29032 into bitcoin:master Nov 17, 2015
gmaxwell added a commit that referenced this pull request Nov 17, 2015
4d29032 Fixed integer comparison warning. (Eric Lombrozo)
luke-jr pushed a commit to luke-jr/bitcoin that referenced this pull request Nov 18, 2015
luke-jr pushed a commit to luke-jr/bitcoin that referenced this pull request Dec 8, 2015
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Sep 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants