00:00:00 --- log: started retro/14.11.18
03:20:26 --- join: Yakety (~lel@41.203.67.132) joined #retro
03:20:35 --- part: Yakety left #retro
06:29:14 --- join: Mat3|coding (~Mat3@ip5b414c9f.dynamic.kabel-deutschland.de) joined #retro
06:29:20 <Mat3|coding> hello
07:08:14 <Mat3|coding> crc: I have the free time to finish the retro port to my VM (I've working on so long) and need some recent documentation for metacompiling retro. What is avariable ?
07:35:10 * Mat3|coding is in the mood to rewrite a retro implementation from scratch
08:08:47 <tangentstorm> heya Mat3|coding 
08:09:09 <Mat3|coding> hi tangentstorm
08:09:16 <tangentstorm> i've been looking into metacompilation too.
08:10:30 <Mat3|coding> fine, I tend to think rewriting retro from scratch would be an easier approach
08:12:38 <Mat3|coding> (at least that would be the Chuck Moore style to do I think)
08:13:09 <Mat3|coding> however I want to avoid it if possible, so what have you found out ?
08:14:49 <tangentstorm> i think the main hurdle is just figuring out what depends on what.
08:15:21 <tangentstorm> but i think that retro can solve that for you by changing the metacompiler.
08:16:39 <tangentstorm> i haven't actually done it yet, but my plan was to modify and extend meta.rx so that when it works through the kernel.rx file, it collects whatever meta-data i want
08:17:01 <Mat3|coding> good idea !
08:17:08 <Mat3|coding> how can I help you ?
08:17:40 <tangentstorm> hrm.
08:17:44 <tangentstorm> i don't know :)
08:18:48 <tangentstorm> i thought i might try to generate a database.
08:19:11 <tangentstorm> my plan was to create a 'database' device
08:19:29 <Mat3|coding> and why look primitives like that:
08:19:31 <Mat3|coding> p: dup dup dup, ;
08:19:34 <Mat3|coding> "( n-nn ) Duplicate TOS" :doc
08:19:36 <Mat3|coding> ???!???
08:20:44 <tangentstorm> i think each word has two names: one for the target image and one for the local image
08:21:01 <tangentstorm> so here the two names are 'dup' and 'dup' and the implementation is  'dup,'
08:21:28 <tangentstorm> or 'lit (whatever the code for dup is) ;;' i guess
08:21:45 <Mat3|coding> ah ok, makes sense, thanks
08:22:27 <tangentstorm> although if i recall, the names are almost always the same
08:22:45 <Mat3|coding> yes, strange solution then
08:23:02 <tangentstorm> maybe it was different at some point. beats me. 
08:24:16 <tangentstorm> meta-alt.rx is meant to be a simplified version of meta.rx, that doesn't depend on the whole retro language.
08:25:01 <tangentstorm> if you look in the Makefile, under the 'image:' recipe, you'll see two lines:
08:25:05 <tangentstorm>         ./retro --shrink --image retroImage --with core.rx
08:25:16 <tangentstorm>         ./retro --shrink --image retroImage --with image/stage2.rx
08:25:55 <tangentstorm> you can 'cp retroImage core.img' in between these to get a stripped down version of the image
08:27:11 <tangentstorm> that's the point where it stops using the old image to generate the new image, and the new image starts running everything itself.
08:38:35 <Mat3|coding> kernel.rx and stage2.rx seem to be straight forward coded, I can use kernel.rx as template and think about replacing the meta compiler with a simple assembler
08:39:07 <Mat3|coding> which can be written in retro itself
08:40:43 <Mat3|coding> my work would be: 1. writing this assembler, 2. port kernel.rx
08:45:07 <tangentstorm> an assembler for your alternate virtual machine?
08:45:13 <Mat3|coding> yes
08:45:17 <tangentstorm> cool
08:54:14 <Mat3|coding> if that's finished you will be able to compile word definations to native code
08:54:22 <tangentstorm> nice!
08:54:46 <Mat3|coding> (and I can use retro as backend for these C compiler which I translate to Nim(rod))
08:55:12 <tangentstorm> :)
09:00:27 * Mat3|coding watching SVFIG meeting record from 14-9-25 beside coding
12:11:06 <beretta> Mat3|coding: where's it at ?
12:11:30 <Mat3|coding> you mean the C compiler
12:11:32 <Mat3|coding> ?
12:14:39 <beretta> no.  Is the SVFIG meeting online somewhere?
12:17:49 <Mat3|coding> http://www.youtube.com/watch?v=NjX9acIN7RA
12:17:52 <Mat3|coding> ^here
12:20:38 <Mat3|coding> as I understand it correctly (bad voice quality) there is even an GreenArrays update declaring there busy working on a larger project (whatever this means)
12:21:04 <beretta> ha... thanks Mat3
12:26:57 <beretta> I remember watching a Chuck Moore vid where he explained some of this programming stuff on GreenArrays and is was bizarre. 
12:32:18 <beretta> hmmm... why does youtube suggest all these conspiracy nut video to me ?
12:35:33 <Mat3|coding> I do not know
12:36:23 <Mat3|coding> I have only a list of SVFIG meeting videos
12:37:17 <Mat3|coding> what have you watched before ?
12:39:57 <beretta> sorry have to go!
13:55:44 <Mat3|coding> ciao
13:56:21 --- part: Mat3|coding left #retro
15:13:59 --- quit: ChanServ (shutting down)
15:17:15 --- join: ChanServ (ChanServ@services.) joined #retro
15:17:15 --- mode: card.freenode.net set +o ChanServ
23:59:59 --- log: ended retro/14.11.18