00:00:00 --- log: started forth/18.07.30 00:06:25 --- quit: proteusguy (Ping timeout: 256 seconds) 00:28:20 --- join: proteusguy (~proteus-g@cm-134-196-84-63.revip18.asianet.co.th) joined #forth 00:28:20 --- mode: ChanServ set +v proteusguy 00:44:23 --- join: ncv (~neceve@2a02:c7d:c5c9:a900:6eaf:6ef7:3b81:d5f6) joined #forth 00:44:23 --- quit: ncv (Changing host) 00:44:23 --- join: ncv (~neceve@unaffiliated/neceve) joined #forth 00:49:21 --- join: tusj (~tusj@185.176.245.13) joined #forth 01:02:45 --- quit: wa5qjh (Ping timeout: 260 seconds) 01:03:00 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 01:04:26 --- join: wa5qjh (~quassel@175.158.225.202) joined #forth 01:04:26 --- quit: wa5qjh (Changing host) 01:04:26 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 01:18:13 --- quit: wa5qjh (Ping timeout: 265 seconds) 02:04:48 --- quit: ashirase (Ping timeout: 240 seconds) 02:05:31 --- join: ashirase (~ashirase@modemcable098.166-22-96.mc.videotron.ca) joined #forth 03:19:21 --- quit: nighty- (Quit: Disappears in a puff of smoke) 03:23:58 --- join: wa5qjh (~quassel@175.158.225.202) joined #forth 03:23:59 --- quit: wa5qjh (Changing host) 03:23:59 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 03:28:18 --- quit: wa5qjh (Ping timeout: 240 seconds) 03:28:32 --- join: wa5qjh (~quassel@175.158.225.202) joined #forth 03:28:32 --- quit: wa5qjh (Changing host) 03:28:32 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 04:07:28 --- join: nighty- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 04:24:59 --- join: dave9 (~dave@90.20.215.218.dyn.iprimus.net.au) joined #forth 05:13:10 --- quit: dave9 (Quit: one love) 05:21:09 --- quit: groovy2shoes (Excess Flood) 05:21:31 --- join: groovy2shoes (~groovy2sh@unaffiliated/groovebot) joined #forth 06:26:30 --- quit: tusj (Ping timeout: 260 seconds) 06:51:56 --- quit: X-Scale (Ping timeout: 240 seconds) 07:00:01 --- join: tusj (~tusj@185.176.245.13) joined #forth 07:07:16 --- quit: tusj (Ping timeout: 268 seconds) 07:13:09 --- join: tusj (~tusj@185.176.245.13) joined #forth 07:29:55 --- join: X-Scale (~ARM@83.223.241.95) joined #forth 07:40:24 --- quit: lchvdlch (Changing host) 07:40:24 --- join: lchvdlch (~nestr0@pdpc/supporter/active/lchvdlch) joined #forth 07:44:58 --- quit: wa5qjh (Quit: http://quassel-irc.org - Chat comfortably. Anywhere.) 07:49:43 --- quit: tusj (Ping timeout: 265 seconds) 07:54:30 regarding the early micro computers. Most I have seen the designs of had seperate address and data buses from the cpu chip. 07:55:44 has anyone seen say 16 bit parallel bus from the cpu been multiplexed between addresses and data? 07:56:36 say, we have 16 pins on the cpu chip for the bus and 3 pins for address strobe, read strobe and write strobe 07:58:37 one could connect the inputs of an JK-latch chip to that bus and use the address strobe as an enable signal to tell it to update. 08:08:01 this enables one to 'break-out' the address bus with something as simple as 16 bit D-Latch chip(s) 08:12:26 like using two 74573 chips for that purpose 08:12:56 sorry wrong part nr 08:15:10 nope, it was correct part nr 08:18:54 --- join: tusj (~tusj@185.176.245.13) joined #forth 09:02:25 --- quit: tusj (Ping timeout: 244 seconds) 09:38:58 --- join: dys (~dys@tmo-104-217.customers.d1-online.com) joined #forth 10:21:15 --- quit: ncv (Ping timeout: 256 seconds) 10:57:58 --- join: Labu (~Labu@labu.pck.nerim.net) joined #forth 11:13:28 --- quit: pierpal (Quit: Poof) 11:13:45 --- join: pierpal (~pierpal@host84-235-dynamic.181-80-r.retail.telecomitalia.it) joined #forth 11:15:36 --- join: tusj (~tusj@185.176.245.13) joined #forth 11:19:52 --- quit: lugh (Quit: quitting bouncer) 11:52:42 --- quit: pierpal (Quit: Poof) 11:53:01 --- join: pierpal (~pierpal@host84-235-dynamic.181-80-r.retail.telecomitalia.it) joined #forth 12:30:02 --- quit: pierpal (Quit: Poof) 12:30:17 --- join: pierpal (~pierpal@host84-235-dynamic.181-80-r.retail.telecomitalia.it) joined #forth 13:02:19 --- join: MickyW (~MickyW@p4FE8DE78.dip0.t-ipconnect.de) joined #forth 13:07:01 --- quit: MickyW (Client Quit) 13:23:16 --- join: lf94 (~lf94@138.197.174.95) joined #forth 13:23:16 --- quit: lf94 (Changing host) 13:23:17 --- join: lf94 (~lf94@unaffiliated/lf94) joined #forth 13:34:41 --- join: pierpa (50b5eb54@gateway/web/freenode/ip.80.181.235.84) joined #forth 14:44:35 --- join: netytan (~marksmith@ip-62-235-176-181.dsl.scarlet.be) joined #forth 14:47:27 Hi all. I'm reading the gforth blocks docs. Can anyone tell me how I'm supposed to understand the stack effect LOAD ( i * x u -- j * x ). My understanding was that LOAD is ( u --), but maybe I'm wrong about that. My question then is why does 1 LOAD work as expected (no stack underflow) from the interpreter? 14:56:31 that means LOAD is ( u -- ) plus the stack effect of the LOADed code 14:57:15 so if there is nothing in block 1 taking more off the stack, that is fine 15:01:14 koisoke: so i*x and j*x just mean, "stuff" ? 15:01:36 yes 15:01:55 Is there any meaning to the letters, i, j and x? 15:03:32 x just means a generic stack entry. i and j are placeholder values 15:04:40 --- join: reepca-laptop (~user@208.89.170.250) joined #forth 15:06:00 koisoke: thanks a lot :-) that makes sense now. (i*x is saying that there are are i generic stack entries on the stack before the load and j*x means there are j generic stack entries on the stack after the load) 15:07:30 ugh, I wish gforth had a clean interface to variadic C functions 15:08:30 It'd be so nice to be able to just put the number of arguments on the top of stack, with the actual variable-arguments underneath it. 15:09:08 it would, yes 15:10:52 all of the provided functions for parsing arguments given from python use varargs... the only way I've seen so far to do it is to provide a pointer to a place for individual parameters to be written to *for every single parameter from python* 15:11:19 Meaning I can't just say "uh, okay, I'll just call it multiple times - first I'll get the first parameter, then I'll get the second parameter..." 15:11:28 I have to actually get all of the parameters at once 15:13:25 It's quite frustrating to know that there were people implementing a non-C language, who should know fully just how frustrating it is to try to interface languages, and still decided to do stuff like use bit fields and varargs everywhere. 15:18:31 I'll just have to hope that the "tuple" they refer to in argument-parsing is the same one as the actual python tuple object, and use those procedures for accessing elements.. 15:29:56 --- quit: epony (Quit: QUIT) 15:33:56 --- quit: pierpal (Ping timeout: 256 seconds) 15:38:36 --- part: netytan left #forth 15:58:54 --- quit: nighty- (Quit: Disappears in a puff of smoke) 16:12:22 --- quit: jn__ (Ping timeout: 248 seconds) 16:50:14 --- join: jn__ (~nope@ip-37-201-200-192.hsi13.unitymediagroup.de) joined #forth 17:15:55 --- join: nighty- (~nighty@kyotolabs.asahinet.com) joined #forth 17:31:44 --- join: epony (~nym@79-100-130-129.ip.btc-net.bg) joined #forth 17:43:46 --- join: pierpal (~pierpal@host84-235-dynamic.181-80-r.retail.telecomitalia.it) joined #forth 17:50:30 --- quit: pierpal (Ping timeout: 248 seconds) 17:56:07 --- quit: dddddd (Remote host closed the connection) 18:08:54 --- join: dave9 (~dave@90.20.215.218.dyn.iprimus.net.au) joined #forth 18:09:16 hi 18:29:38 --- join: wa5qjh (~quassel@175.158.225.202) joined #forth 18:29:50 --- quit: wa5qjh (Changing host) 18:29:50 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 18:39:21 brb 20:10:13 --- quit: dave9 (Quit: one love) 20:37:22 --- quit: pierpa (Quit: Page closed) 21:12:49 --- join: pierpal (~pierpal@host84-235-dynamic.181-80-r.retail.telecomitalia.it) joined #forth 21:14:29 --- quit: pierpal (Client Quit) 21:14:44 --- join: pierpal (~pierpal@host84-235-dynamic.181-80-r.retail.telecomitalia.it) joined #forth 21:38:49 --- join: dave9 (~dave@90.20.215.218.dyn.iprimus.net.au) joined #forth 23:07:30 --- quit: dys (Ping timeout: 260 seconds) 23:59:59 --- log: ended forth/18.07.30