00:00:00 --- log: started retro/11.03.25
07:14:47 --- join: aisa (~aisa@c-68-35-165-60.hsd1.nm.comcast.net) joined #retro
10:19:21 --- quit: aisa (Quit: aisa)
11:30:40 --- join: roarde (~roarde@pdpc/supporter/active/roarde) joined #retro
12:19:18 --- quit: roarde (Quit: Leaving)
13:52:30 --- join: roarde (~roarde@pdpc/supporter/active/roarde) joined #retro
14:51:45 <roarde> crc: Please describe the "target audience" for Retro.
14:51:56 <roarde> (or anyone else can take a stab)
15:10:40 --- quit: jdp (Read error: Connection reset by peer)
16:13:52 <crc> me :)
16:14:45 <crc> or more precisely, people who want a small, forth-style language that is portable, reasonibly practical, and portable, even if limited in terms of interacting within existing systems
16:15:26 <crc> (and understandable; it's my intention that retro remain small enough for a single person to be able to learn the entire thing, and modify it to meet their specific needs)
16:16:18 <roarde> which single person is that?
16:17:03 <roarde> Sorry, I'm frustrated.
16:17:22 <crc> again, I developed it mostly for my own purposes
16:17:26 <roarde> Goes without saying, there are prerequisites to learning Retro.
16:17:53 <crc> things should be easier to learn as the documentation improves
16:17:58 <roarde> Right, and the best stuff is started that way and stays that way.
16:18:45 <roarde> "best stuff" is one's own for oneself, even when shared
16:20:26 <crc> I'm finally happy with retro (11); it does what I want, the language is reasonibly clean, and more stable than before.
16:22:02 <roarde> Reasonably sure it's been used enough to announce a feature freeze soon?
16:22:16 <crc> yes
16:24:15 <roarde> I still think Ngaro in Retro's a good idea.
16:25:16 <crc> I may do that once I have the docs in better shape
16:25:26 <roarde> True that the practical way now is to glue it on top of another vm
16:25:33 <crc> it'd be useful as part of autopsy (for debugging)
16:26:05 <roarde> but having it lets one understand Retro thoroughly by learning only Retro.
16:26:40 <crc> true
16:27:47 <roarde> In other words, my thinking is it should sit there and look pretty rather than being in normal use.
16:38:13 <crc> the only difficult bits would be loading and saving the image. I'll have to read it in and assemble bytes into cells. Slow, but doable
16:48:40 <crc> roarde: I'll have a basic version done in a couple of days
16:51:45 <roarde> For my use, I'll be coming up with material on some of the basics - but I have to get in first.
16:52:29 <roarde> right now, going for coffee
17:07:45 <crc> I'll include comments in the retro.rx source
17:08:04 <crc> start of the code @ http://sprunge.us/CLBc
19:08:54 <crc> http://sprunge.us/USbM - enough of a start to actually begin running code in the image
19:22:43 --- quit: roarde (Quit: Leaving)
23:59:59 --- log: ended retro/11.03.25