00:00:00 --- log: started retro/08.12.10
04:36:27 --- quit: nighty__ (Client Quit)
05:42:01 --- quit: nighty^ (Read error: 104 (Connection reset by peer))
05:45:12 --- join: nighty^ (n=nighty@x122091.ppp.asahi-net.or.jp) joined #retro
05:50:10 --- quit: virl (Remote closed the connection)
07:45:31 --- quit: nighty^ (Excess Flood)
07:46:03 --- join: nighty^ (n=nighty@x122091.ppp.asahi-net.or.jp) joined #retro
08:16:48 --- quit: nighty^ (Read error: 110 (Connection timed out))
08:27:34 --- join: nighty^ (n=nighty@x122091.ppp.asahi-net.or.jp) joined #retro
11:09:45 --- join: virl (n=virl__@chello062178085149.1.12.vie.surfer.at) joined #retro
12:15:43 --- join: neceve (n=ncv@dyn-89.136.41.150.tm.upcnet.ro) joined #retro
14:46:44 --- quit: neceve (Remote closed the connection)
15:20:21 --- join: sixforty (n=sixforty@204.110.227.11) joined #retro
16:41:13 --- join: kpatrick (n=chatzill@S0106001346a41b69.vf.shawcable.net) joined #retro
16:41:36 <sixforty> hi kpatrick
16:41:43 <kpatrick> hi
16:42:37 <sixforty> how goes it with your java implementation?
16:44:48 <virl> people are writing java implementations?
16:45:55 <sixforty> If I remember correctly, kpatrick is looking at it.
16:46:02 <kpatrick> good.  I am studying another java implementation called JForth, written by Craig A. Lindley to get some ideas
16:46:11 <kpatrick> hi virl, yes
16:46:58 <virl> you mean.. forth on java?
16:47:07 <virl> and I thought you write a java vm
16:47:19 <kpatrick> I implemented ngaro vm in java.  
16:47:30 <kpatrick> there was an existing implementation which I modified
16:47:43 <virl> I meant a JAVA-VM
16:47:59 <sixforty> you were thinking java on forth, virl?
16:48:05 <kpatrick> the existing impl had some issues.  I also added a debugger.
16:48:12 <virl> sixforty, no.
16:48:26 <virl> sixforty, just writing a damn stupid JAVA-VM 
16:48:31 <virl> in say C
16:48:34 <virl> or whatever..
16:49:34 <sixforty> it has its uses
16:50:22 <virl> sixforty, I'm also writing a forth with the name, let the original name hit you(what was that called? I think sarcasm), gameforth. 
16:50:33 <virl> sixforty, yes it has it's uses.
16:51:09 <kpatrick> one change I made may be useful to backport to the C version.  In my version, the instruction pointer is incremented as part of the op, not as part of the loop.  This has some benefits 
16:51:10 <kpatrick> 		case OP_DROP:
16:51:12 <kpatrick> 			popDataStack();
16:51:13 <kpatrick> 			ip++;			
16:51:15 <virl> sixforty, but what I meant was that I know a lot of other vms which are probably much more fun to implement say, forth, lisp, smalltalk, etc.
16:51:15 <kpatrick> 			break;
16:51:22 <sixforty> virl: you lost me in the middle of the sentence. not hard to do, I'm afraid
16:53:35 <sixforty> as I'm still working on 'hello world' in c and don't do java, I don't see how you're doing it, but what you're doing seems to be a favorite topic of debate in forth.
16:53:37 <kpatrick> if you look at retro.forth  in the dev kit you see this 
16:53:39 <kpatrick> : execute   1-, push, ;    
16:53:41 <kpatrick> the 1- is required because of the extraneious increment in the loop   in my version this becomes
16:53:42 <kpatrick> : execute  push, ;
16:57:39 <sixforty> so, is gameforth a forth for games or forth as a game?
16:59:50 <kpatrick> I think Factor also started out as a scripting environment for a game. 
17:02:29 --- join: nighty__ (n=nighty@210.188.173.245) joined #retro
17:04:48 <virl> sixforty, I had a brainfart, sorry-
17:05:41 <virl> it's intended to be a forth for games.
17:06:14 <virl> but instead of slava I don't want to lose my game target 
17:07:14 <sixforty> how do you plan to access hardware; vid cards, for example?
17:07:19 <virl> also this forth system is more a forth than Factor is, Factor is more an RPN lisp.
17:08:13 <virl> I want to use syscalls, for the targeted platform, that's not something very insane.
17:08:28 <sixforty> I was just introducing myself to factor. Nice. Not to my taste.
17:09:20 <sixforty> 'targeted platform' or 'targeted platforms'?
17:10:23 <sixforty> better, more direct question is (ignore the other) will it be written in C?
17:10:31 <kpatrick> virl have you looked at forth on the gamecube    http://gcforth.blogspot.com/
17:12:16 <kpatrick> btw:  I haven't seen crc around.  anybody know what's up?  maybe he is just taking a break.
17:12:44 <sixforty> his internet connection at home is unusable right now
17:16:51 <sixforty> I just found GameForth on forthfreak. Either of those yours, virl?
17:18:45 <virl> nope.
17:18:58 <virl> as I said a stupid name.
17:19:04 <virl> already taken by hundreds
17:19:15 <sixforty> . . . ah. That was the basis of 'original . . . sarcasm' remark then?
17:19:23 <virl> like my other forth, which is the base of gameforth "bootforth"
17:19:52 <virl> yes
17:20:20 <virl> which is as I know the bootloader for FreeBSD
17:20:34 <sixforty> Looks like I've caught up, finally. Will miracles never cease? :P
17:21:10 <virl> hmm?
17:21:21 <virl> sry, I don't get that sentence
17:22:16 <sixforty> I was still scrolled up the page trying to understand your original post. My brain unlocked just long enough to catch up with what you were saying.
17:24:50 <sixforty> I'm thinking about porting retroforth to dosbox.
17:27:26 <sixforty> Once I have a few useful retro apps, I'd port small portions of dosbox to, yes, dos. Just to have access to hardware without dealing with permissions.
17:28:29 <virl> and I'm thinking about getting that crazy code box, which I wrote running on the ARM through selfcompilling hell. damn it.
17:30:03 <virl> well, good night
17:30:08 --- quit: virl ("Verlassend")
19:53:14 --- quit: sixforty ("Leaving.")
21:56:33 --- join: kpatrick_ (n=chatzill@S0106001346a41b69.vf.shawcable.net) joined #retro
22:01:29 --- quit: kpatrick (Read error: 145 (Connection timed out))
22:01:44 --- nick: kpatrick_ -> kpatrick
23:26:26 --- part: kpatrick left #retro
23:59:59 --- log: ended retro/08.12.10