--- Log opened Tue Oct 30 00:00:51 2018
01:36 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Ping timeout: 256 seconds]
01:38 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #secp256k1
02:20 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]
03:25 -!- kallewoof [~quassel@240d:1a:759:6000:a7b1:451a:8874:e1ac] has quit [Read error: Connection reset by peer]
03:27 -!- kallewoof [~quassel@fp96f94c66.tkyc515.ap.nuro.jp] has joined #secp256k1
03:36 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #secp256k1
03:56 -!- kallewoof [~quassel@fp96f94c66.tkyc515.ap.nuro.jp] has quit [Read error: Connection reset by peer]
03:58 -!- kallewoof [~quassel@240d:1a:759:6000:a7b1:451a:8874:e1ac] has joined #secp256k1
04:02 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 256 seconds]
04:03 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #secp256k1
04:43 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]
04:44 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #secp256k1
04:52 -!- ken2812221 [~ken281222@110.50.135.178] has quit [Remote host closed the connection]
04:53 -!- ken2812221 [~ken281222@110.50.135.178] has joined #secp256k1
05:01 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 256 seconds]
05:03 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #secp256k1
08:58 < nickler> Are there arguments for deciding between (size_t)-1 and SIZE_MAX besides some people finding the former more readable, some the latter?
09:03 < andytoshi> i don't think anyone finds (size_t)-1 more readable, the argument for it is purely whether the compiler would accept SIZE_MAX
09:03 < andytoshi> i had thought we were compiling in C89 mode (which is why all our variables are declared at the top of functions, etc) and that we didn't have SIZE_MAX
09:06 < gmaxwell> ::sigh::
09:06 < gmaxwell> We are C89. Yes.
09:06 < gmaxwell> And we use stdint.h. This is not incompatible with using C89.
09:06 < gmaxwell> The codebase uses stdint.h types _everywhere_.  Every uintNN_t is a stdint type.
09:07 < nickler> compiles for me ;P
09:07 < gmaxwell> This means that if you use a really archane C compiler you may have to provide a copy of stdint.h yourself.
09:07 < andytoshi> gmaxwell: i didn't know SIZE_MAX was in stdint.h
09:07 < andytoshi> you would think it'd be in stddef.h with size_t
09:08 < gmaxwell> In practice, actual C89 only 'embedded' compilers still have stdint in any case.
09:08 < gmaxwell> andytoshi: ah. unless I'm really confused (always possible), it's a stdint.h thing, specified at the same time as the uintxx_t maximums.
09:09 < andytoshi> initial google results suggest you're right, it's in stdint
09:10 < andytoshi> from http://pubs.opengroup.org/onlinepubs/009695399/basedefs/stdint.h.html "The <stdint.h> header shall declare sets of integer types having specified widths, and shall define corresponding sets of macros. It shall also define macros that specify limits of integer types corresponding to types defined in other standard headers. "
11:27 -!- deusexbeer [~deusexbee@095-129-169-142-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 252 seconds]
11:28 -!- deusexbeer [~deusexbee@080-250-075-157-dynamic-pool-adsl.wbt.ru] has joined #secp256k1
12:16 -!- reallll [~belcher@unaffiliated/belcher] has joined #secp256k1
12:19 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 244 seconds]
12:38 -!- ddustin [40470882@gateway/web/freenode/ip.64.71.8.130] has joined #secp256k1
13:42 -!- reallll is now known as belcher_
17:08 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
18:47 -!- ddustin [40470882@gateway/web/freenode/ip.64.71.8.130] has quit [Ping timeout: 256 seconds]
23:19 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]
23:27 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #secp256k1
--- Log closed Wed Oct 31 00:00:52 2018