00:00:00 --- log: started retro/13.05.16 00:38:51 --- join: impomatic (~digital_w@43.22.125.91.dyn.plus.net) joined #retro 04:10:13 --- quit: impomatic (Ping timeout: 256 seconds) 05:19:45 --- quit: ivan``_ (Remote host closed the connection) 05:24:09 --- join: impomatic (~digital_w@87.112.130.90) joined #retro 05:27:09 --- join: ivan`` (~ivan@unaffiliated/ivan/x-000001) joined #retro 08:23:04 --- join: crc (~crc@li125-93.members.linode.com) joined #retro 08:32:35 --- join: tangentstorm (~michal@108-218-151-22.lightspeed.rcsntx.sbcglobal.net) joined #retro 11:34:55 --- quit: goingretro (Read error: Connection reset by peer) 11:40:09 --- join: goingretro (~kbmaniac@host86-186-154-2.range86-186.btcentralplus.com) joined #retro 11:44:39 --- join: Mat2 (~claude@91-65-144-133-dynip.superkabel.de) joined #retro 11:45:05 good day ! 11:49:24 --- quit: sirdancealo2 (Quit: Ragequit) 11:56:51 heya Mat2 11:57:15 hi tangentstorm 11:57:32 take a look at reforth: http://aerosuidae.net/reforth/ 11:57:49 oh yeah. i've seen that before 11:57:52 what about ti? 11:57:54 it? 11:58:06 its a forth to C compiler 11:59:20 something like llvm with interpretative backend 11:59:27 oh i didn't realize that. i thought it was just written in c. 12:01:41 well, just look at the examples 12:01:59 the editor for example 12:03:06 where? 12:03:41 found it 12:05:15 good stuff in the editor. 12:05:47 I think this editor can be easily ported to retro 12:10:41 looking at the compiler source now. interesting. 12:11:26 seems like c would make an odd choice for a target since its own calling conventions would get in the way... 12:11:52 unless you just compiled goto statements... 12:19:33 I agree, it is an limitation which can't be avoided 12:21:19 reforth also do not support any dynamic features of forth 12:22:34 (unless you write an interpretative run-time system) 13:39:24 --- join: ncv (~quassel@79.114.120.25) joined #retro 13:39:24 --- quit: ncv (Changing host) 13:39:24 --- join: ncv (~quassel@unaffiliated/neceve) joined #retro 13:42:52 parable.py is mostly functional (still needs a garbage collector, some type conversions, and debugging) 13:43:46 code is at http://forthworks.com/parable/active/py/ or lp:~crc-x/+junk/parable-in-python 13:49:02 is forthworks your site, crc? 13:50:11 yes 13:51:45 AddType text/plain py in your httpdconf / .htaccess will make those python files readable online 13:52:42 that's cool. i'd seen the wiki before but didn't know it was your site :) 13:59:43 #1 #2 #3 * #4 + 13:59:59 -> 0 # 1.0 ; 1 # 10.0 14:00:20 is that right? 14:00:56 * tangentstorm fails arithmetic 14:03:30 pretty cool :) 14:05:48 thanks for the AddType; it's done now 14:06:41 ah cool :) 14:47:38 crc: thanks for the link 14:51:51 --- join: sirdancealo2 (~sirdancea@98.82.broadband5.iol.cz) joined #retro 14:52:44 * Mat2 thinks of using the genie language for a quick port and then use compilers assembly output as base for nasm 14:55:48 ok, I make a direct assembler port, it is easier 15:08:29 --- quit: ncv (Remote host closed the connection) 15:16:39 ciao 15:16:43 --- quit: Mat2 (Quit: Verlassend) 17:33:39 --- quit: karswell (*.net *.split) 17:33:50 --- quit: sirdancealo2 (*.net *.split) 17:33:52 --- quit: saper (*.net *.split) 17:38:26 --- join: sirdancealo2 (~sirdancea@98.82.broadband5.iol.cz) joined #retro 17:38:26 --- join: saper (saper@wikipedia/saper) joined #retro 17:52:06 --- join: karswell (~user@46.208.83.73) joined #retro 18:03:09 --- join: beretta (~beretta@cpe-107-8-120-203.columbus.res.rr.com) joined #retro 18:21:50 --- quit: beretta (Ping timeout: 264 seconds) 23:59:59 --- log: ended retro/13.05.16