00:00:00 --- log: started retro/06.09.16 00:02:07 --- quit: lukeparrish (Read error: 110 (Connection timed out)) 00:45:09 --- quit: Quartus (Read error: 104 (Connection reset by peer)) 01:08:33 --- quit: Raystm2 (Read error: 104 (Connection reset by peer)) 01:11:21 --- join: Raystm2 (n=NanRay@adsl-69-149-62-42.dsl.rcsntx.swbell.net) joined #retro 03:17:45 --- quit: neceve (Remote closed the connection) 03:20:47 --- join: neceve (n=claudiu@unaffiliated/neceve) joined #retro 03:42:01 --- mode: ChanServ set +o Raystm2 05:13:20 --- join: Quartus (n=trailer@CPE0001023f6e4f-CM013349902843.cpe.net.cable.rogers.com) joined #retro 08:40:32 --- nick: lukeparr1sh -> lukeparrish 09:34:26 --- join: Cheer1 (n=Cheery@a81-197-19-23.elisa-laajakaista.fi) joined #retro 09:34:53 --- nick: Cheer1 -> Cheery_ 09:35:28 --- quit: Cheery (Nick collision from services.) 09:35:36 --- nick: Cheery_ -> Cheery 09:41:38 --- quit: timlarson ("Leaving") 09:42:28 --- join: timlarson (n=timlarso@user-12l325b.cable.mindspring.com) joined #retro 10:47:01 crc: have you found out an nice interface for file input/output? 11:05:23 I have basic file I/O in place 11:05:33 z" filename" MODE file.open 11:05:50 that gives you a file handle that allows for reading/writing or closing of the file 11:06:59 basically a wrapper over fopen(), fread(), fwrite(), and fclose(). 11:29:54 and now "include" has been coded and works :) 11:54:35 --- join: snoopy_1711 (i=snoopy_1@dslb-084-058-105-058.pools.arcor-ip.net) joined #retro 11:56:12 excellent, crc, I've a small plan for your new retro. 11:56:35 cool 11:56:55 * crc will send it out before running to the store (expect it within the next 5-10 minutes) 11:57:30 ok, I may send you my plan trough email if you don't have time to hear it now. 11:57:47 please do 11:57:48 and I was just about to ask. :) 11:58:24 but one thing. 11:58:34 do you happen to know a bit about C ABI? 11:58:52 how does the functions look like? 11:59:02 for Linux/BSD, on 32-bit x86 I know a fair amount 11:59:26 it's pretty sane, unlike C++ ABI :) 11:59:29 for linux I'd like to know. 11:59:40 I've understood so. 12:00:07 just simply, how does it handle the parameters and return? 12:00:37 the return value is stored in eax 12:00:47 parameters are passed on the hardware stack 12:01:18 what is the hardware stack, or do you use it in retro? 12:01:21 parameters are pushed from right to left 12:01:28 hardware stack = return stack in retro 12:01:40 call/ret uses it, push/pop also does 12:02:04 that's intresting! Thank you. :) 12:02:23 The function that calls another function cleans up the stack when it's done. 12:02:37 those are the basic rules, I can expand on them later if you want 12:03:05 ok. but I think I'll go with these. 12:03:22 ok. Glad I could help. 12:06:23 rxforth 0L has been sent 12:06:49 * crc shall return sometime tonight 12:11:43 --- quit: Snoopy42 (Read error: 110 (Connection timed out)) 12:12:06 --- nick: snoopy_1711 -> Snoopy42 13:24:03 --- quit: Cheery ("Download Gaim: http://gaim.sourceforge.net/") 16:24:07 --- quit: virl (Remote closed the connection) 17:15:41 --- quit: neceve (Remote closed the connection) 18:05:05 crc: congrats on RxForth 0L, neat. 18:11:30 --- join: jas2o (n=jas2o@WNPP-p-203-54-32-119.prem.tmns.net.au) joined #retro 18:30:15 --- quit: jas2o ("jas2o.forthworks.com") 19:01:23 --- join: nighty_ (n=nighty@CPE00119576a9c5-CM0012c90d36fc.cpe.net.cable.rogers.com) joined #retro 20:52:46 --- quit: nighty_ ("Disappears in a puff of smoke") 21:04:45 --- join: airbrush (i=airbrush@216-237-193-86-access.northstate.net) joined #retro 21:48:24 --- join: virl (n=virl@chello062178085149.1.12.vie.surfer.at) joined #retro 22:03:55 --- quit: timlarson ("Leaving") 22:17:05 --- join: timlarson (n=timlarso@user-12l325b.cable.mindspring.com) joined #retro 22:56:03 --- join: Cheery (n=Cheery@a81-197-19-23.elisa-laajakaista.fi) joined #retro 23:59:59 --- log: ended retro/06.09.16