Just include "valve_minmax_off.h" before including algorithm.
2014-07-18 22:26 GMT+02:00 Borzh <borz...@gmail.com>: > I just include <algorithm> and that breaks everything (I don't need to use > min/max of course). > I just was writing external plugin for source and I don't really know all > valve internals. > Just prefer use STL, which I know is an awesome (and well tested in all > ways) library. > > > 2014-07-18 16:48 GMT-03:00 Skyler York <sky...@gmail.com>: > > Quick side note, but you can wrap std::min/max in parenthesis to prevent >> macro expansion. It's not pretty but it works: >> >> (std::max)(a, b); >> >> >> On Fri, Jul 18, 2014 at 11:33 AM, Tony "omega" Sergi <omegal...@gmail.com >> > wrote: >> >>> I don't understand why you need to use stl at all.. when the reason why >>> it's incompatible, is because pretty much every use of stl has been wrapped >>> by valve functions in order to tie it all into the memory manager. tier1 is >>> full of engine compatible containers and whatnot for anything you could >>> need to do. >>> >>> >>> On Fri, Jul 18, 2014 at 9:20 PM, Borzh <borz...@gmail.com> wrote: >>> >>>> I had to undefine it, undefine MINMAX_H also, so it could be included >>>> after that and then include minmax.h manually. >>>> Anyway it is ugly solution and macros should be written in uppercase to >>>> not confuse with methods. >>>> >>>> >>>> 2014-07-17 21:25 GMT-03:00 Dexter Haslem <dexter.has...@gmail.com>: >>>> >>>> why not just undefine it before STL headers? >>>>> >>>>> On Thu, Jul 17, 2014 at 11:33 AM, Borzh <borz...@gmail.com> wrote: >>>>> > Hello all, >>>>> > >>>>> > I propose using template functions in minmax.h instead of defines. >>>>> Or at >>>>> > least use uppercase letters for macros. >>>>> > >>>>> > It has been discussed a lot of times: >>>>> > - windows.h defines min/max, it is ugly, ok but I thought Valve is >>>>> not >>>>> > Microsoft. At least for Windows you can #define NOMINMAX before >>>>> include >>>>> > windows.h. >>>>> > >>>>> > - Valve's minmax.h defines min/max and you can't use STL because it >>>>> tries to >>>>> > apply macros to std::min and std::max which breaks everything!!! >>>>> Can't avoid >>>>> > it, because Valve use this macros everywhere!!! >>>>> > >>>>> > If someone from Valve is reading this, please do something, it is >>>>> awful !!! >>>>> > >>>>> > Thanks, >>>>> > Boris. >>>>> > >>>>> > _______________________________________________ >>>>> > To unsubscribe, edit your list preferences, or view the list >>>>> archives, >>>>> > please visit: >>>>> > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlcoders >>>>> > >>>>> > >>>>> >>>>> _______________________________________________ >>>>> To unsubscribe, edit your list preferences, or view the list archives, >>>>> please visit: >>>>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlcoders >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> To unsubscribe, edit your list preferences, or view the list archives, >>>> please visit: >>>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlcoders >>>> >>>> >>>> >>> >>> >>> -- >>> -Tony >>> >>> _______________________________________________ >>> To unsubscribe, edit your list preferences, or view the list archives, >>> please visit: >>> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlcoders >>> >>> >>> >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlcoders >> >> >> > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlcoders > > >
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlcoders
