00:00:00 --- log: started forth/10.03.03 00:08:46 --- quit: proteusguy (Ping timeout: 256 seconds) 00:25:13 --- join: proteusguy (~proteusgu@zeppelin.proteus-tech.com) joined #forth 00:52:51 --- join: ygrek (debian-tor@gateway/tor-sasl/ygrek) joined #forth 01:32:29 --- join: dinya_ (~Denis@94.50.162.193) joined #forth 01:34:49 --- quit: _dinya__ (Ping timeout: 260 seconds) 02:24:36 --- join: mathrick (~mathrick@users177.kollegienet.dk) joined #forth 02:28:55 --- quit: nighty__ (Remote host closed the connection) 02:55:03 --- join: _mathrick (~mathrick@users177.kollegienet.dk) joined #forth 02:58:33 --- quit: mathrick (Ping timeout: 240 seconds) 03:14:32 --- quit: kar8nga (Read error: Connection reset by peer) 03:18:24 --- nick: _mathrick -> mathrick 03:24:59 --- quit: mathrick (Ping timeout: 246 seconds) 03:27:37 --- join: mathrick (~mathrick@users177.kollegienet.dk) joined #forth 03:45:44 --- join: arke (~arke@169.237.101.216) joined #forth 04:14:38 Hi. 04:39:30 hai arke 04:39:32 --- quit: proteusguy (Ping timeout: 246 seconds) 04:40:06 --- quit: ASau (Ping timeout: 252 seconds) 04:52:59 --- join: proteusguy (~proteusgu@zeppelin.proteus-tech.com) joined #forth 06:21:45 --- quit: dinya_ (Read error: Connection reset by peer) 06:23:06 --- join: dinya_ (~Denis@94.50.162.193) joined #forth 06:29:20 Good morning / afternoon / evening. Morning for me. 06:32:24 --- quit: foxes (*.net *.split) 06:36:54 --- join: foxes (~flash@61.149.172.1) joined #forth 06:45:06 Hey, on these processors that have an A register when you say VARIABLE ALPHA does ALPHA then put the variable address directly into the A register? So that you could say ALPHA ! in the usual way? 06:57:35 You've broken one-to-one correspondence already, why ask? 07:32:36 Um, because I'd like to know? 07:35:27 Well... You've stepped onto little known soil. 07:35:33 You're on your own now. 07:36:20 Each deviation from mainstream Forth may make compiler harder to write. 07:46:36 KipIngram: I'm not aware of any that put newly created variables in the A register 07:46:38 Fair enough. But VARIABLE is pretty easy to support. You'd just compile the PFA of the variable word, as usual, as a nested subroutine call. When it calls that spot it will load the three opcodes stored there and *leave IP pointed at the next cell*. That happens to be the address you want for the variable. So you'd just need an opcode that would either load IP into A, or put IP on the stack so you 07:46:40 could then load it into A. So the code might be IP@ A! RET. 07:47:36 Actually IP->A is a better thing to have. Then for variable you'd have IP->A RET, and for constant you'd have IP->A @ RET 07:49:31 If IP went to the stack then you'd need IP@ A! @ RET for a constant; the fourth opcode would spill into the next cell, so you'd waste space. 07:51:37 ASau: re: little-known soil; I presumed that since the MuP21 and the C18 both use an A register that there was some known work in this area. I assume someone has written a compiler for these chips? 08:14:27 Hey, the MuP21 doesn't have >R, R>, or R@. But it looks like >R and R> are back on the C18. 08:15:36 On the C18, is the P register the program counter? 08:18:08 As best I can tell it is. I don't understand the utility of the !p+ and @p+ instructions. 08:19:46 Oh, I guess that's right along the lines of the stuff I just mentioned re: variables and constants. If you called a subroutine that sat just in front of a constant, for instance, you could @p+ ret to put the value on the stack. 08:21:38 And you could do a variable by putting the address inline, so just inserting @p+ in your code would put that address on the stack. 08:22:09 --- nick: madwork_ -> madwork 08:23:13 It looks like you'd do those things without changing the value of your A or B registers. That's nice; my way overwrote A every time you executed a constant or variable word. 08:28:40 --- join: TR2N (email@89-180-169-215.net.novis.pt) joined #forth 08:54:50 --- join: Quartus` (~Quartus`@74.198.8.58) joined #forth 09:34:18 --- join: ASau (~user@83.69.227.32) joined #forth 09:46:59 --- join: kar8nga (~kar8nga@jol13-1-82-66-176-74.fbx.proxad.net) joined #forth 09:59:13 --- quit: ygrek (Ping timeout: 245 seconds) 10:07:22 --- quit: proteusguy (Ping timeout: 276 seconds) 10:14:12 --- quit: kar8nga (Remote host closed the connection) 10:20:08 --- join: proteusguy (~proteusgu@zeppelin.proteus-tech.com) joined #forth 10:24:19 --- join: forther (~forther@207.47.34.100.static.nextweb.net) joined #forth 10:24:42 hi all 10:25:27 hi forther 10:27:13 hi 10:35:12 --- join: kar8nga (~kar8nga@jol13-1-82-66-176-74.fbx.proxad.net) joined #forth 10:38:49 hi 11:40:10 --- quit: ASau (Ping timeout: 248 seconds) 11:43:51 --- quit: kar8nga (Remote host closed the connection) 11:50:51 --- join: ASau (~user@83.69.227.32) joined #forth 12:02:24 --- join: Maki_ (~Maki@dynamic-213-198-207-96.adsl.eunet.rs) joined #forth 12:06:42 --- quit: madwork (Ping timeout: 252 seconds) 12:21:59 --- join: madwork (~madgarden@204.138.110.15) joined #forth 12:36:57 --- quit: Quartus` (Ping timeout: 252 seconds) 12:57:29 --- join: Quartus` (~Quartus`@74.198.8.59) joined #forth 13:39:19 --- quit: Maki_ (Quit: Leaving) 14:04:19 --- quit: forther (Quit: Leaving) 14:31:16 --- quit: Quartus` (Ping timeout: 276 seconds) 15:57:48 --- join: crc_ (~charlesch@71.23.210.149) joined #forth 16:01:05 --- quit: crc (Disconnected by services) 16:01:09 --- nick: crc_ -> crc 16:01:14 --- mode: ChanServ set +o crc 16:22:05 --- join: nighty__ (~nighty@210.188.173.245) joined #forth 19:37:38 --- quit: proteusguy (Read error: Operation timed out) 19:56:26 --- join: proteusguy (~proteusgu@zeppelin.proteus-tech.com) joined #forth 20:28:14 --- quit: Deformative (Remote host closed the connection) 20:28:39 --- join: Deformative (~joe@c-76-112-68-135.hsd1.mi.comcast.net) joined #forth 20:44:48 --- quit: proteusguy (Ping timeout: 252 seconds) 21:03:03 --- join: proteusguy (~proteusgu@zeppelin.proteus-tech.com) joined #forth 22:38:26 --- join: |dinya_| (~Denis@94.50.162.193) joined #forth 22:41:21 --- quit: dinya_ (Ping timeout: 240 seconds) 22:55:04 --- quit: proteusguy (Ping timeout: 258 seconds) 22:59:04 --- join: kar8nga (~kar8nga@jol13-1-82-66-176-74.fbx.proxad.net) joined #forth 23:07:43 --- join: vlekkie (~phillip@84-104-203-195.cable.quicknet.nl) joined #forth 23:08:23 are there any bindings in forth allowing me to create a native win32 and/or a native cocoa window? 23:14:10 --- join: proteusguy (~proteusgu@zeppelin.proteus-tech.com) joined #forth 23:33:59 --- quit: proteusguy (Ping timeout: 268 seconds) 23:36:15 --- join: proteusguy (~proteusgu@zeppelin.proteus-tech.com) joined #forth 23:38:55 --- quit: proteusguy (Excess Flood) 23:41:06 --- join: ygrek (debian-tor@gateway/tor-sasl/ygrek) joined #forth 23:50:04 --- join: proteusguy (~proteusgu@zeppelin.proteus-tech.com) joined #forth 23:55:58 vlekkie: some forths have that, yes. 23:56:12 vlekkie: but it's not in any way standard 23:59:59 --- log: ended forth/10.03.03