00:00:00 --- log: started retro/06.07.06
00:10:12 --- quit: Snoopy42 (clarke.freenode.net irc.freenode.net)
00:14:56 --- join: Snoopy42 (i=snoopy_1@dslb-084-058-150-087.pools.arcor-ip.net) joined #retro
03:21:06 --- join: Cheery (i=Henri@a81-197-12-134.elisa-laajakaista.fi) joined #retro
08:36:40 <docl> good morning
10:13:20 <Cheery> oh. morning!!!!
10:13:23 <Cheery> !!!!!
10:13:25 <Cheery> !!!!!!!!!!!!!!!!!!!!!!!!!!
10:35:21 * docl yawns
10:44:53 <Cheery> sorry, I had to do that.
10:47:26 <docl> :)
10:47:46 <docl> almost noon here, now
10:57:06 <docl> hmm. crc says linux syscalls not relating to multitasking/multithreading could be built into the existing retro native. I wonder how hard multitasking support would be to implement.
10:58:31 <virl> perhaps a special version of the interpreter?
10:58:47 <docl> gtk (or a minimal subset) could likely be ported without multitasking. seems like
10:59:41 <docl> yeah, maybe multiple instances of the boot loop that are cycled through continuously, and which refer to different areas of memory
11:01:34 <virl> well, or threading...
11:02:13 <virl> so one interpreter cycles through a list of words which need to get executed.
11:02:38 <virl> I think that's the interesting one and simpler one 
11:02:46 <docl> might work
11:03:18 <docl> would they need to exist in different environments (dict, heap, stack, etc.)?
11:03:39 <virl> no, for threading that's one thing.
11:04:21 <virl> hell! that can be easily done, I mean, only manipulating the ui word.
11:04:47 <docl> yeah seems like it could
11:07:05 <docl> but it seems like if you had two concurrent programs running at the same time you would need to save the stack state, and use a different heap/pad, etc. before switching.
11:09:14 <docl> that wouldn't be too hard though
11:29:21 <virl> that's why we are men and love forth ;-)
11:29:29 <docl> threads are when you don't switch memory contexts?
11:29:40 <docl> tasks are when you do?
11:29:46 <virl> threads are lightweight processes
11:30:00 <virl> and task are normally processes
11:30:23 * docl is reading the wikipedia entry on multitasking
11:30:28 <virl> processes have their own stuff, like their own stack, their own heap and so on.
11:30:41 <virl> threads share those things.
11:31:03 <virl> (iirc)
11:31:29 <docl> I think you're right, from what I'm reading
11:31:41 <docl> those words had me confused before, but now it makes sense :)
11:40:28 <docl> a thread has to be more careful about what it does with the stack, heap, etc. than a full-fledged task, I gather?
11:42:17 <virl> jep.
11:42:36 <virl> (that's why they are horrible to debug)
11:42:52 <docl> ahh, I see.
12:02:53 <Cheery> yes, but threads are also only way of doing some things right.
12:03:04 <Cheery> or should we talk about processes and tasks.
12:03:54 <virl> yeah, thinks like input
13:50:45 <docl> I wonder if we will attempt to emulate linux multitask/multithread syscalls, or make our own.
14:34:15 <virl> perhaps over linux it's faster
14:39:36 --- quit: Cheery ("Leaving")
15:17:12 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-148-104.pools.arcor-ip.net) joined #retro
15:25:31 --- quit: Snoopy42 (Read error: 145 (Connection timed out))
15:25:42 --- nick: snoopy_1711 -> Snoopy42
15:34:17 <crc> good evening
15:50:06 <crc> should I open a repository for the rdml tools?
16:38:29 <docl> how much trouble would that be?
16:43:02 <docl> do you like the idea of having several repositories? might be good.
17:12:13 <docl> hmm, from what I'm seeing of the make process, gtkhtml seems rather bloated
17:22:00 <docl> 50 megs after compilation. must be using a ton of external libs.
17:22:53 <crc> ouch
17:23:16 * crc will look elsewhere 
17:24:35 <crc> http://retroforth.org/repos/rdml
17:32:05 <docl> nice
17:33:26 <crc> as to having multiple repositories, that is trivial
17:33:41 <crc> darcs get <url>
17:33:54 <crc> and you have a copy of the full repository
17:43:07 <docl> that's neat
17:43:25 <docl> I like that they are browsable from the web
17:45:30 <crc> yup
17:46:25 * docl has been using xfce4 lately
17:47:18 <crc> I'm running blackbox
17:47:43 <crc> though I am thinking of trying 9wm again
17:48:15 <docl> it's fun to try the various wm's out.
17:48:47 <docl> I just started using screen for my terminals, it's very nice.
17:49:19 <docl> I can transport my session to any terminal I want, i.e. from X to a vt and back
17:53:53 <crc> screen doesn't seem to be in pkgsrc :(
17:54:41 <docl> darn. it's a gnu project, fairly old...
17:55:22 <crc> found it (under 'misc')
17:55:34 <docl> cool :)
17:56:47 <docl> the main keypress you use a lot in screen is control-a.
18:05:07 <crc> cool, I have a splitscreen :)
18:15:44 <crc> http://retroforth.org/stacked.png
18:17:31 <docl> nice :)
18:18:22 * docl just temporarily crashed screen while attempting to use split
18:21:10 <docl> afk, pizza
23:59:59 --- log: ended retro/06.07.06