00:00:00 --- log: started retro/08.01.27
02:33:13 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #retro
02:39:18 --- quit: virl ("Verlassend")
02:54:27 --- join: Cheery (n=cheery@a91-155-222-68.elisa-laajakaista.fi) joined #retro
09:26:00 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #retro
09:26:17 <virl> hi crc, are you there?
10:03:24 <crc> yes
10:18:19 --- quit: Quartus ()
10:43:33 --- join: Quartus (n=neal@CPE0001023f6e4f-CM001947482b20.cpe.net.cable.rogers.com) joined #retro
10:55:35 <virl> well, I told you that I wrote a framework for writing prototypes of a forth system. which I called bootforth
10:55:51 <virl> how do you like the idea?
11:00:23 <crc> what makes it different than existing implementations of Forth?
11:01:39 <virl> that it's not a forth system in itself, but a framework for creating one.
11:02:00 <virl> and that it's only intended for bootstrapping
11:02:15 <crc> ok
11:02:40 <crc> the 'bootforth' name is already used by freebsd and dragonfly bsd for their ficl-based bootloader
11:03:01 <crc> I'd like to see the framework when it's ready to share
11:03:32 <virl> well, do you have a better name in mind?
11:04:04 <crc> no
11:06:53 <virl> btw. how do you define in that context 'ready to share'?
11:07:09 <crc> when you are ready to share the code :)
11:08:31 <virl> well, it's GPLv3, there is documentation(probably old now), also a running interpreter. hmm.. 
11:09:08 <crc> ok
11:11:33 <virl> I think I'll put it on the empty xell webspace
11:12:49 <crc> ok
11:14:20 <virl> the base primitives work, just something like does> gives me a little bit of pondering.
11:18:51 <crc> I haven't implemented does> for retro10 yet
11:22:07 <virl> how does it work generally?
11:23:49 <crc> in old versions of retro, create would compile a call do "dovar"; does> would patch this to call "dodoes", which was an internal routine that did some adjustments to call the code after does>. It was a bit tricky
11:25:08 <crc> there's an implementation for rf9.x done by Quartus in rfans.zip (http://quartus.net/retro/rfans.zip)
11:28:24 <crc> in retro10, does> will be optional, along with most words I'll end up writing for it
11:34:14 <virl> will be optional?
11:34:28 <virl> what do you mean with that?
11:34:37 <virl> (exactly)
11:34:47 <crc> most words in retro10 will be optional
11:35:35 <crc> the core image consists of around 80 words, providing a basic interpreter and compiler with simple I/O functionality. Graphics, expanded conditionals, etc are all optional pieces that can be compiled in if desired.
11:39:12 <virl> nice idea
11:39:55 <virl> how much of it do you have implemented yet?
11:40:17 <crc> the core is functional
11:40:32 <crc> I've begun working on the optional stuff now, and started documenting the core
11:40:38 <crc> see http://retro.tunes.org
11:40:46 <crc> and http://docs.google.com/View?docid=dhs99d59_9d4r9k9cz&pli=1 for the documentation on the core
11:41:05 <crc> http://retro.tunes.org/repos/retro is the darcs repository, which can be viewed online
11:41:43 <crc> the only require file to build a new image is retro.toka
11:42:09 <virl> ngaro?
11:43:29 <crc> a portable virtual machine that retro10 runs on
11:44:01 <crc> it's a stack-based architecture, with a MISC-style instruction set
11:45:09 * crc has to go for a little while, will be back
11:55:06 --- join: Guest9548915 (i=snoopy_1@dslb-088-068-195-235.pools.arcor-ip.net) joined #retro
12:03:19 --- quit: Snoopy42 (Read error: 145 (Connection timed out))
12:03:19 --- nick: Guest9548915 -> Snoopy42
12:04:50 --- quit: ChanServ (calvino.freenode.net irc.freenode.net)
12:16:13 --- join: ChanServ (ChanServ@services.) joined #retro
12:16:13 --- mode: irc.freenode.net set +o ChanServ
12:20:40 --- quit: ChanServ (Shutting Down)
12:23:27 --- join: ChanServ (ChanServ@services.) joined #retro
12:23:27 --- mode: irc.freenode.net set +o ChanServ
12:41:46 --- quit: Quartus ()
12:50:10 <virl> crc, did you write ngaro?
12:55:00 --- join: Quartus (n=neal@CPE0001023f6e4f-CM001947482b20.cpe.net.cable.rogers.com) joined #retro
13:03:14 <crc> yes
13:04:50 <crc> I actually wrote most of ngaro in 2006, then finished it during the last few months of 2007
13:05:09 <crc> I then spent a couple of weeks writing the initial implementation of retro10's core
13:06:19 <virl> ngaro is your start point for retro, as bootforth is for my forth implementation
13:07:16 <crc> retro will be implemented for various platforms, not just ngaro
13:09:35 <crc> I ported an older, incomplete version of the core to 32-bit x86 Linux already
13:14:45 <virl> cool
13:15:25 <virl> whatever, I'm happy to see bootforth in a good direction so that I can start building my own forth implementation
13:15:58 <virl> my real implementation 
13:16:52 <virl> btw. I haven't used classes for a long long time, for what were they again?
13:29:38 <crc> word classes are special words that do something with xt's
13:29:58 <crc> specifically, they define the actions taken to carry out on an xt
13:30:44 <virl> interesting..
13:31:32 <virl> bootforth uses something like that
13:31:54 <virl> but I haven't called it classes.
13:37:19 <virl> I use the code field and the data field, the code field defines what the word should do and so on. I think that's the classic way of doing that in a forth system
13:44:48 --- quit: Cheery ("Lost terminal")
14:52:28 <crc> my dictionary headers have four fields: link to previous header, class, xt, and name
21:32:31 --- quit: virl ("Verlassend")
23:22:46 --- join: Cheery (n=cheery@a88-113-54-18.elisa-laajakaista.fi) joined #retro
23:59:59 --- log: ended retro/08.01.27