00:00:00 --- log: started retro/12.04.25 02:13:07 --- quit: jyf1987 (Quit: leaving) 02:51:57 --- quit: __tthomas__ (Ping timeout: 260 seconds) 09:22:02 --- join: __tthomas__ (~Owner@24.130.7.34) joined #retro 09:47:28 --- join: impomatic (~digital_w@108.171.125.91.dyn.plus.net) joined #retro 10:10:03 <__tthomas__> crc here is experiment did yesterday with local stack and coroutine like functions.. http://pastebin.com/XpdQUjeT 10:35:00 --- quit: impomatic (Quit: impomatic) 12:28:35 --- quit: __tthomas__ (Ping timeout: 265 seconds) 12:44:28 --- join: __tthomas__ (~Owner@24.130.7.34) joined #retro 13:16:51 should strings be distinct from character arrays? 13:20:56 --- join: Mat2 (~dambere@91-64-133-197-dynip.superkabel.de) joined #retro 13:21:02 hello 13:22:57 <__tthomas__> hey Mat2 13:23:08 <__tthomas__> I got my experiment working 13:24:00 hi tthomas 13:24:30 you mean a third stack as inter-word interface ? 13:24:47 <__tthomas__> yeah, and used as coroutines 13:25:50 <__tthomas__> http://pastebin.com/XpdQUjeT 13:26:13 <__tthomas__> It was surprisingly easy 13:28:31 classic forth style :) 13:29:06 <__tthomas__> heh 13:29:48 <__tthomas__> it looks more like factor than forth to me... 13:31:06 I mean the factoring 13:31:58 <__tthomas__> it was fun to work on, actually used curry.. 13:35:04 <__tthomas__> one nice thing is pop is nondestructive so if you are just using it to store arguments to particular instance of word all you have to do is update stack pointer after pop arguments.. 13:35:26 it's useful so should be basis for a library 13:35:44 <__tthomas__> yeah, a very short library, think it would only be about 6 lines.. 13:37:02 <__tthomas__> seems to work decently for lightweight cooperative threading.. 13:39:24 <__tthomas__> I think I am going to add a status variable though, I don't like relying on top of stack for passing success failure.. 13:40:52 would be good 13:42:08 if I found the time I add a time-based multitasker, would just need slightly changes 13:42:45 and the sources are there, from these fig forth I mention yesterday 13:53:37 <__tthomas__> yeah, I have seen implementations using user variables, like f83 has a well documented multitasker.. 13:54:12 <__tthomas__> then gforth has minioop which is super simple forth oop... though I think with struct library and quotes you get more or less same benefits.. 14:14:05 probably 14:25:32 need some sleep, ciao 14:25:35 --- part: Mat2 left #retro 17:17:13 --- join: Kumul (~Kumul@cvx-ppp-66-50-147-89.coqui.net) joined #retro 17:17:37 --- part: __tthomas__ left #retro 23:06:25 --- quit: Kumul (Quit: gone) 23:55:56 --- join: jyfl987 (~jyf@unaffiliated/yunfan) joined #retro 23:59:59 --- log: ended retro/12.04.25