00:00:00 --- log: started retro/10.09.20 00:02:03 --- quit: roarde (Quit: Leaving.) 05:21:46 --- quit: crcx (Ping timeout: 245 seconds) 06:18:55 --- join: roarde (~sixforty@pdpc/supporter/active/sixforty) joined #retro 07:27:46 --- join: crcx (~crc@li125-93.members.linode.com) joined #retro 07:30:48 --- quit: crc (Ping timeout: 252 seconds) 07:32:21 --- join: crc (~charlesch@184.77.185.20) joined #retro 10:45:09 --- join: fengye110 (7051d8b0@gateway/web/freenode/ip.112.81.216.176) joined #retro 10:45:49 hello guys 10:45:58 hi, fengye110 10:47:11 can i use forth in linux 10:47:24 for learn 10:47:54 Yes, but I don't know which forth to recommend for learning. 10:48:24 retro builds very easily on linux, but there's not enough help for beginners 10:48:30 I'm facing the same problem. 10:50:11 i'a learning retro 10:50:30 http://christophe.lavarenne.free.fr/ff/ (see "Primer") or 10:50:55 http://dev.ronware.org/p/reva/doc/tip/www/main.wiki 10:51:38 But if it's retro you want, just get it from the stable link in the topic. 10:52:38 3q, i will try it later 10:52:43 extract it, cd to retro-10.7.1, and type "make" 10:53:20 get it 10:53:26 ./retro runs it, bye (space) exits. Read doc/Glossary.txt 10:55:47 what about the book "Starting FORTH" ? 10:56:06 starting forth is very out of date 10:56:32 is there something mvp-ish that runs on linux? 10:56:56 oh. http://forthfreak.net 10:57:03 i don't konw 10:58:15 I should've specified "crcx". :) He's probably at work right now, though. Other things to do than chat. 10:58:42 roarde: I try to watch the logs when it's slow 10:59:13 yeah, if I ask a q and disappear, I pick up any answers in logs 11:17:59 I try to answer questions if I see them in the logs 12:00:17 --- quit: roarde (Quit: Leaving.) 12:13:58 --- quit: fengye110 (Quit: Page closed) 12:16:06 --- join: fengye110 (7051d8b0@gateway/web/freenode/ip.112.81.216.176) joined #retro 12:16:18 what about gforth 12:16:46 is it a good start to learn forth 12:17:51 gforth isn't bad 12:19:45 and which is good 12:20:19 your advice? 12:25:06 gforth is ans compliant, so you'll be more likely to find tutorial material for it, and support can be found on the comp.lang.forth newsgroups 12:25:57 reva is not ans compliant, but its developer is quite helpful. support is done by a mailing list, and I think they have some tutorial material 12:27:11 I offer support for retro here, or in the #forth channel, and also via a mailing list and forums 12:29:08 got it. thanks 12:30:00 --- quit: fengye110 (Quit: Page closed) 13:23:16 hi 13:47:13 hi erider 15:23:45 at home now 18:04:06 hi crc whats up 18:53:53 erider: not much 18:54:07 I did a little work on the sqlite bindings today; fixing them for the latest image 18:54:28 nice :) 18:55:15 docl: I also updated your tab completion code for the latest image 18:55:16 coll 18:55:18 cool 18:56:38 I'll probably start backporting some of the new stuff into the 10.7.x codebase soon 19:09:24 wow jacob navia has a solid c compiler 19:14:51 which compiler? 19:15:21 * erider is very please with the lcc-win32 compiler 19:16:08 if you have to use windows that is most definitely the compiler of choose 19:17:03 I use a mingw gcc compiler (for c) and gmcs (for c#) from mono 19:17:46 gmcs is on linux 19:18:04 gmcs is part of mono, so linux, windows, and mac os x 19:18:36 crc you coding in c#? 19:19:06 erider: just a little, to maintain the c# implementation of the vm 19:19:50 neat I guess I can't get out the past C forever :( 19:32:06 C isn't bad 19:36:25 * docl is working on an article about the biases of computer programming, for Less Wrong 19:37:41 http://openetherpad.org/iSPfFgH95h 19:38:15 programming actually seems to reduce cognative bias more than not. the question is whether there is some particular kind of bias that is increased by it. 19:38:43 crc are you still working on the webapps 19:41:12 docl: will read in a minute 19:41:19 erider: on and off 19:43:09 docl: very true 19:46:32 any ideas on what to add? 20:08:33 offhand, not really. then again, I have been up for awake for around 22 hours now, and am getting a bit tired :( 20:08:48 that's ok 20:08:55 thanks for your contributions so far :) 20:09:18 collaborative editing is interesting. 20:15:40 this is way better than earlier attempts. I recall using a collaborative editor a couple of years back that was brutally slow and inelegant. 20:41:44 off to bed. I'll take another look at this tomorrow. 20:41:57 ok, see ya 20:42:00 sleep well 21:36:10 --- quit: crc (Ping timeout: 252 seconds) 21:36:43 --- join: crc (~charlesch@184.77.185.20) joined #retro 23:59:59 --- log: ended retro/10.09.20