06:58:25  * rendarjoined
08:12:57  * saghuljoined
08:24:42  * saghulquit (Quit: My MacBook has gone to sleep. ZZZzzz…)
10:25:11  * mylesborinsquit (Quit: farewell for now)
10:25:42  * mylesborinsjoined
14:33:22  * jshanabjoined
14:34:25  <jshanab>I have been looking at a way to pool buffers in libuv like mentioned here; http://www.howtobuildsoftware.com/index.php/how-do/WHC/c-memory-memory-management-libuv-libuv-allocated-memory-buffers-re-use-techniques
14:36:05  <jshanab>I do not like one aspect of that. there is only char* and length. Is that the length of the allocated or used area. If I am going to re-use it I need a capacity and a used otherwise I will be continuously resizing the buffer, which could defeat the pool concept.
14:39:01  <jshanab>It looks like the alloc_cb will provide the len of the actual data and so I can easily aquire the next buffer of suffient size, I jsut loose the capacity information for the release step without now a lookup.
14:44:55  * rendarquit (Ping timeout: 246 seconds)
18:04:51  * jshanabquit (Quit: ChatZilla 0.9.90.1-rdmsoft [XULRunner 1.9.0.17/2009122204])
20:30:07  * ncthom91joined
21:05:49  * ncthom91quit (Quit: My MacBook has gone to sleep. ZZZzzz…)
21:52:17  * jshanab_quit (Quit: ChatZilla 0.9.93 [Firefox 55.0.1/20170809080026])
23:25:21  * bytekittenjoined