Skip to content

Conversation

@Diapolo
Copy link

@Diapolo Diapolo commented May 18, 2012

This does things better than the first commit, which had a bug and placed define strncasecmp _strnicmp in an #ifndef WIN32 in init.cpp. Sorry for this.

src/init.cpp Outdated
Copy link
Member

Choose a reason for hiding this comment

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

Rather move this to an #else under the #ifndef WIN32...

Copy link
Author

Choose a reason for hiding this comment

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

Good point, will do this.

@Diapolo
Copy link
Author

Diapolo commented May 18, 2012

Updated to reflect suggestion from @luke-jr.

@gavinandresen
Copy link
Contributor

NACK. It would be better to get rid of usage of strncasecmp all together and use boost's case-insensitive string support.

E.g.
- if (strlen(argv[i]) > 7 && strncasecmp(argv[i], "bitcoin:", 8) == 0)
+ if (boost::algorithm::istarts_with(argv[i], "bitcoin:"))

istarts_with is in boost/algorithm/string/predicate.hpp

@Diapolo
Copy link
Author

Diapolo commented May 19, 2012

@gavinandresen Are you fine with massive boost usage now? I will update that pull and use what you suggested, no problem.

@Diapolo
Copy link
Author

Diapolo commented May 19, 2012

Closed in favor of #1363!

@Diapolo Diapolo closed this May 19, 2012
@gavinandresen
Copy link
Contributor

RE: "massive boost usage" :

I'm all for making the code clearer and more cross-platform, and we're dependent on boost anyway. The string algorithms are nice little self-contained pieces of functionality.

But I'm on the fence for changes like sipa's pull request that uses boost::variant for bitcoin addresses (and requires writing little visitor classes to do simple things). I think template metaprogramming is the wrong way to go, it makes code hard to debug, creates cryptic compiler messages, etc.

And I was using boost's compile-time regex library for a pull request, but one of the reasons it never got pulled was because it would increase compile times and memory usage when compiling.

@laanwj
Copy link
Member

laanwj commented May 20, 2012

creates cryptic compiler messages, etc.

One nitpick: you could use clang. In contrary to gcc, it has wonderfully clear error messages, even with template metaprogramming. Also it compiles much faster.

But I agree that usage of boost should improve readability, not decrease it.

And compile-time work is great for time-sensitive inner loops that need to be optimized for specific cases, but using it unnecessarily increases code size and compile time.

suprnurd pushed a commit to chaincoin-legacy/chaincoin that referenced this pull request Dec 5, 2017
- allow filtering by all signals in `list`
- do not count/print funding votes for watchdogs
lateminer pushed a commit to lateminer/bitcoin that referenced this pull request Jan 22, 2019
[fix for miner_tests.cpp] Initialize nThreads in parallel.cpp
lateminer pushed a commit to lateminer/bitcoin that referenced this pull request May 6, 2020
3f98b37 [CMake] Check for and require Qt 5.5.1 minimum version (Fuzzbawls)
19ce9de build: Refactor out Qt version check macro (Fuzzbawls)
2c18e82 Bump minimum required Qt to 5.5.1 (Fuzzbawls)

Pull request description:

  As per bitcoin#1292, this effectively bumps the minimum required Qt version to 5.5.1.

  - Removed no longer needed precompiler conditionals
  - Updated autotools to check for and require at least 5.5.1 to build the GUI
  - Updated CMake to check for and require at least 5.5.1 to build the `pivx-qt` target

  Closes bitcoin#1292

ACKs for top commit:
  random-zebra:
    ACK 3f98b37
  furszy:
    looking good, utACK 3f98b37

Tree-SHA512: 32e494ea7f166ce57a9be08dbfcc067546f4e0c46ccc8b9a4836dd148243ca14e1fede166cccdb6ae6ddbae8f0832362a6935e42742ed957b41be3104511bdd0
lateminer pushed a commit to lateminer/bitcoin that referenced this pull request May 6, 2020
9450439 build: remove extra tokens warning (Fuzzbawls)
ebb4da9 build: fix m4 escaping (Fuzzbawls)
2b3b9c3 doc: proper capitalize terms (Fuzzbawls)
efee3fc build: remove duplicated QT_STATICPLUGIN define (Fuzzbawls)

Pull request description:

  Further cleanups to the Qt m4 file that I wanted to keep separate from bitcoin#1351

ACKs for top commit:
  random-zebra:
    ACK 9450439
  furszy:
    ACK 9450439

Tree-SHA512: 1d8c0194eb72116ea4ee414c31cec8a6f472c3493a0aa63e456188aff3a2c20b8871fba22b27947ebd303b0ebe42b86a2cbaed42d3ee424a69088d8e61070b34
lateminer pushed a commit to lateminer/bitcoin that referenced this pull request May 6, 2020
c54fd9d [Qt] Switch to newer connect syntax (Fuzzbawls)

Pull request description:

  Switch all Qt connections to the newer functor-based syntax.

  Marked [WIP] for now until larger PRs can be merged.

  Mostly ported from bitcoin#13529

  Requires the following PR to be merged first in order to adhere to standards:
  - [x] bitcoin#1351

ACKs for top commit:
  furszy:
    ACK c54fd9d
  random-zebra:
    ACK c54fd9d and merging...

Tree-SHA512: d5222264566a8920ab97e8c586f134156d9d0514d014b430bdd47a34b0620ab94a1c6d341b6a57322f1131a8fad91a5e1af907f3bd7112d0ab5e04c4cc9f5ae5
@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.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants