IRC Logs for #io Monday, 2014-09-08

*** bjz_ has quit IRC00:13
*** gatesphere has quit IRC02:07
*** NetBeast has quit IRC02:12
prologicjer: hey :) interviews go well?04:39
prologicio: was thinking last night / this morning — I don’t suppose you’d be interested at all in actually helping me write my mio-rewrite implemtnation? :)04:40
*** ryanu has quit IRC05:28
*** hashmal has joined #io05:34
*** hashmal has quit IRC07:34
jerprologic, next one is wednesday, and yeah so far going great07:37
jerand no not really interested in that atm07:38
jer1:40am time to sleep07:38
prologicjer, no worries :)08:25
prologicgood luck again :)08:25
*** NetBeast has joined #io09:04
*** TheMonkey has joined #io09:58
*** ElMonkey has quit IRC10:01
*** bjz has joined #io10:56
*** hashmal has joined #io11:16
*** ijon_ has joined #io12:01
*** hashmal has quit IRC12:28
*** hashmal has joined #io12:29
*** hashmal has quit IRC12:34
*** fredreichbier has joined #io13:24
*** NetBeast has quit IRC15:17
*** hashmal has joined #io18:25
*** ijon_ has quit IRC18:46
*** fredreichbier has quit IRC19:45
*** hashmal_ has joined #io21:22
*** hashmal has quit IRC21:22
*** TheMonkey has joined #io22:23
*** ryanu has joined #io22:39
*** gatesphere has joined #io22:41
*** hashmal_ has quit IRC22:43
prologicjer: quick question. if I’m parsing an Io-style grammar with the eventual goal of compiling the ast to a sequence of bytecode instructions; why do I need to build a parse tree? why can’t we just have a linear list of messages?23:00
prologicin my first attempt (pure python); I built a parse tree with messages pointing from one to the next, etc with an evaluator; but really this simply boils down (or could) to a list of messages with the evaulator operating on a sequence of messages23:01

Generated by 2.11.0 by Marius Gedminas - find it at!