00:25:26  * caitpjoined
00:32:45  * rendarquit
01:43:37  * dpinojoined
02:50:12  * plutoniixquit (Quit: จรลี จรลา)
03:23:09  * octetcloudquit (Ping timeout: 245 seconds)
04:39:51  * caitpquit (Ping timeout: 250 seconds)
05:06:44  <trungl-bot>Tree closed by [email protected]: Tree is closed (Automatic: "Check" on http://build.chromium.org/p/client.v8/builders/V8%20Mac%20-%20debug/builds/1817 "V8 Mac - debug" from c67dab62c7db38a31de853418874d99b7ae97a3b: [email protected])
05:09:17  * stalledquit (Ping timeout: 245 seconds)
05:19:51  * stalledjoined
05:38:47  * caitpjoined
05:47:01  <trungl-bot>Tree opened by [email protected]: Tree is open (flake...)
06:10:29  * caitpquit (Ping timeout: 246 seconds)
06:29:23  * dpinoquit (Ping timeout: 246 seconds)
06:29:26  * wingojoined
06:56:02  * plutoniixjoined
06:56:46  * plutoniixquit (Max SendQ exceeded)
06:57:15  * plutoniixjoined
06:58:54  * plutoniixquit (Max SendQ exceeded)
06:59:26  * plutoniixjoined
07:01:03  * plutoniixquit (Max SendQ exceeded)
07:01:36  * plutoniixjoined
07:03:04  * plutoniixquit (Max SendQ exceeded)
07:03:55  * plutoniixjoined
07:12:55  * plutoniixquit (Read error: Connection reset by peer)
07:28:40  * dpinojoined
07:46:43  * plutoniixjoined
08:04:50  * mostynbjoined
09:11:28  * Lethalmanjoined
09:14:42  * muellijoined
09:21:53  * plutoniixquit (Quit: จรลี จรลา)
09:42:29  * muelliquit (Read error: Connection reset by peer)
09:55:31  * caitpjoined
10:26:07  * caitpquit (Ping timeout: 256 seconds)
10:32:58  * bnoordhuisjoined
11:00:56  * bnoordhuisquit (Ping timeout: 272 seconds)
11:08:03  * Net147joined
11:52:58  * caitpjoined
12:25:19  * caitpquit (Ping timeout: 255 seconds)
12:27:52  * bnoordhuisjoined
12:47:21  * Net147quit (Quit: HydraIRC -> http://www.hydrairc.com <- Nine out of ten l33t h4x0rz prefer it)
12:56:42  * bnoordhuisquit (Ping timeout: 256 seconds)
12:57:43  * plutoniixjoined
13:01:53  * caitpjoined
13:12:17  * dpinoquit (Ping timeout: 246 seconds)
13:31:37  * plutoniixquit (Read error: Connection reset by peer)
13:33:23  * plutoniixjoined
13:41:20  * Lethalmanpart ("Sto andando via")
14:17:38  * caitpquit (Ping timeout: 265 seconds)
14:35:36  * jonaslundjoined
14:36:09  <jonaslund>is there a way to make sure that maximum optimizations are enabled for a piece of code with V8 when testing ?
14:37:05  <jonaslund>right now i just do 5 dry runs of expensive functions (testing under node.js) before timing things
15:14:16  * caitpjoined
15:27:16  * bnoordhuisjoined
15:47:11  * RT|Chatzillaquit (Quit: ChatZilla 0.9.86.1 [Firefox 2.0.0.22pre/2009081014])
15:48:28  * caitpquit (Ping timeout: 272 seconds)
15:55:55  * octetcloudjoined
16:01:07  * mooseboobsjoined
16:05:23  * mostynbquit (Quit: Leaving)
16:23:01  * jonaslundquit (Ping timeout: 252 seconds)
16:30:15  * xiinotulpjoined
16:33:19  * plutoniixquit (Ping timeout: 256 seconds)
16:44:30  * wingo_joined
16:46:07  * wingoquit (Ping timeout: 250 seconds)
16:46:53  * caitpjoined
17:04:07  * KillerJimjoined
17:16:13  <caitp>so what's happening to the issue tracker for v8 and chromium if google code is shutting down?
17:43:32  * jonaslundjoined
18:00:26  * wingo_changed nick to wingo
18:27:21  * mooseboobs_joined
18:27:31  * mooseboobsquit (Ping timeout: 250 seconds)
18:27:37  * enaqxquit (Ping timeout: 244 seconds)
18:29:53  * enaqxjoined
18:34:38  * mooseboobs_quit (Ping timeout: 246 seconds)
18:44:09  * mooseboobsjoined
18:59:58  * enaqxquit (Ping timeout: 255 seconds)
19:04:11  * mooseboobsquit
19:15:57  * enaqxjoined
19:47:45  * enaqxquit (Ping timeout: 265 seconds)
20:02:14  * enaqxjoined
20:32:50  * jonaslundquit (Ping timeout: 272 seconds)
20:33:52  * jonaslundjoined
20:41:04  * wingoquit (Ping timeout: 272 seconds)
21:03:39  * jonaslundquit (Ping timeout: 244 seconds)
21:16:04  * jonaslundjoined
21:33:12  * enaqxquit (Ping timeout: 264 seconds)
21:47:54  * enaqxjoined
22:28:11  * RT|Chatzillajoined
22:32:13  * muellijoined
22:38:49  * muelliquit (Ping timeout: 264 seconds)
22:45:12  * jonaslundquit (Ping timeout: 264 seconds)
22:46:28  * mostynbjoined
22:48:23  * octetcloudquit (Ping timeout: 252 seconds)
22:55:40  * xiinotulpquit (Ping timeout: 256 seconds)
22:56:04  * jonaslundjoined
23:02:30  * xiinotulpjoined
23:04:28  * octetcloudjoined
23:06:53  * mkrufkyjoined
23:09:40  <mkrufky>in the context of node.js c++ bindings, is there ANY way to build a json object outside of the main thread? I'm considering using libjsoncpp to build the objects and convert them to v8 in my main thread callbacks, but the thought of that makes me cringe a bit. it would be awesome to have some way to build a v8 json object in a worker thread and not actually activate it until the main thread is woken.... is there any such method?
23:19:55  * jonaslundquit (Ping timeout: 252 seconds)
23:25:34  * jonaslundjoined
23:31:06  <jonaslund>mkrufky: you mean a string array containing actual JSON data or a deserialization of such a thing into regular JAVASCRIPT objects that can be accessed from the script ?
23:31:54  <mkrufky>the latter ... deserialization into javascript objects to be accessed by the js
23:32:24  <mkrufky>although i COULD build a json STRING in the worker thread and convert it into a v8 json object in my main thread callback
23:32:33  <mkrufky>but i was hoping for something prettier
23:36:14  * KillerJimquit (Quit: Leaving)