00:00:00 --- log: started retro/13.11.02 11:06:53 today i will finally start building a database with entries for each defined word in retro. 11:28:10 Cool 11:28:42 I'll be moving most of the documentation to markdown in the next week or so. 11:29:39 --- join: crcx (uid2647@gateway/web/irccloud.com/x-wevxqbyngxfpdanm) joined #retro 11:29:56 --- nick: crcx -> crc_mobile 11:30:13 i haven't given up on retro pascal either.. just been working on other parts 11:30:43 i want to look at this too: http://www.teamten.com/lawrence/projects/turbo_pascal_compiler/ 11:31:19 I've been working on parable, and doing some (very) preliminary work on moving away from meta compiling the kernel. 11:32:36 and moving toward what instead? (i'm not entirely sure what you mean) 11:34:53 I'd like to be able to build a functional initial image that doesn't start from the previous one. A simple, non-interactive compiler for a subset of retro, with implementations in c and python 11:37:26 oh! yes! i want that too :) 11:40:47 one reason i'm making the database is so I can make a dependency graph for the words. I'd like to find the shortest possible path to a working listener, even if it can't do basic things like division or whatever yet :) 11:43:33 653 lines is already pretty darn short though (kernel.rx)... the file seemed huge and overwhelming when i was first learning... 12:22:20 tracking dependencies is useful. I have parable builds that can dump out source with just the necessary bits included, but nothing for retro. 12:22:58 Though to be fair, retro makes this much more difficult to achieve due to the more complex compiler and optimization 12:23:06 And header less functions... 12:33:33 yeah, :) i'm basically going through and adding start/end tags on everything... or at least writing a program to help me do that 23:59:59 --- log: ended retro/13.11.02