Use of min and max in Gil conflicts with Win32-API on Windows/MSVC about gil HOT 4 CLOSED

We use (min)() etc. in Math and Multiprecision...

I'm used to this trick as well.

I’ll just PR the trivial changes tonight

Thank you. I'm sure nobody will object it and your PR will be merged. Especially, that we had accepted similar fixes e.g. #328

BTW, AFAICT, we mix both workarounds, the () and the NOMINMAX e.i. 87b7fdb The former is more portable, of course, as build system agnostic.

from gil.

Thanks @ckormanyos for reporting this.
Although (min)() is a fine solution, I'm always unclear what is the Boost-wide convention to handle this annoyance. Do you perhaps know? I'd prefer to follow solution that is widely adopted by Boost developers and known to Boost users.

from gil.

what is the Boost-wide convention to handle this annoyance. Do you perhaps know?

We use (min)() etc. in Math and Multiprecision. When I just started boosting, I learned or thought I learned from @jzmaddock that this parenthesis-based workaround is the Boost way.

from gil.

I’ll just PR the trivial changes tonight and you can decide at your convenience if it’s a go or no-go.

from gil.