Continues #8105.
Review of this should be pretty straight forward. Just compare binaries. View the diff in visual diff or so.
To provide tested ACK, cherrypick paveljanik@5d2f98e and compare master build log and this PR build log.
Continues #8105.
Review of this should be pretty straight forward. Just compare binaries. View the diff in visual diff or so.
To provide tested ACK, cherrypick paveljanik@5d2f98e and compare master build log and this PR build log.
386@@ -387,7 +387,7 @@ bool CDB::Rewrite(const string& strFile, const char* pszSkip)
387 while (fSuccess) {
388 CDataStream ssKey(SER_DISK, CLIENT_VERSION);
389 CDataStream ssValue(SER_DISK, CLIENT_VERSION);
390- int ret = db.ReadAtCursor(pcursor, ssKey, ssValue, DB_NEXT);
391+ ret = db.ReadAtCursor(pcursor, ssKey, ssValue, DB_NEXT);
Technically speaking, this is not directly function scope.
But yes, one view is to have only one return value variable, the other is one return value variable per function call.
Renaming ret
to ret1
here could make this particular change smaller.
objdump -d $bin
returns the same binaries for me on d5b25fa
paveljanik
laanwj
MarcoFalke
sipa
Labels
Refactoring
Wallet