00:00:00 --- log: started forth/17.10.11 00:01:53 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 00:02:49 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 00:02:50 --- nick: wa5qjh_1 -> wa5qjh_ 00:05:38 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 00:07:19 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 00:07:58 --- nick: wa5qjh_1 -> wa5qjh_ 00:18:15 wa5qjh: AFAIK closest to bare metal on RPi is OpenWRT. http://jeelabs.org/2016/02/dive-into-forth/ 00:20:37 OpenWRT is Forth based? Did not know that. as long as that's been around to!! 00:20:46 --- quit: wa5qjh_ (Remote host closed the connection) 00:21:04 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 00:21:07 do you know of any other forth with ssh[d] support? 00:21:37 or ability to work with wifi nic cards ? 00:25:39 --- quit: wa5qjh_ (Ping timeout: 255 seconds) 00:26:10 OpenWRT has nothing in common with Forth. It is just a tiny Linux distro. 00:26:30 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 00:30:28 https://github.com/organix/pijFORTHos 00:31:03 --- quit: wa5qjh_ (Ping timeout: 255 seconds) 00:32:39 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 00:35:30 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 00:36:54 --- quit: wa5qjh_ (Ping timeout: 255 seconds) 00:38:42 that looks interesting!! 00:39:34 ( dang CRS. been trying to remember the phrase 'bare metal' all day!! ) 00:39:57 --- quit: wa5qjh_1 (Ping timeout: 255 seconds) 00:41:29 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 00:43:31 I've got some documentation on the broadcom SoC too, sad thing about that seems to be no A/D input on it. guess nobody ever saw need for it. 00:45:36 wa5qjh: Do You know about https://github.com/mark4th/t4 ? 00:45:48 --- quit: wa5qjh_ (Ping timeout: 255 seconds) 00:50:56 --- quit: wa5qjh (Remote host closed the connection) 00:53:26 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 00:53:31 I have looked into the HC12 and HC08 families, but they seem to be on the way out. 00:54:31 --- join: leaverite (~quassel@175.158.225.198) joined #forth 00:54:31 --- quit: leaverite (Changing host) 00:54:31 --- join: leaverite (~quassel@freebsd/user/wa5qjh) joined #forth 00:54:54 --- nick: leaverite -> wa5qjh_ 00:58:49 --- quit: wa5qjh (Ping timeout: 240 seconds) 00:59:25 DKordic I just had to reboot. too many tabs open! 00:59:26 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 01:03:37 Thanks for the info. I gotta look into that one. both of them actually.. 01:03:49 --- quit: wa5qjh (Ping timeout: 240 seconds) 01:04:36 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 01:05:36 I know I could probably get a ( near) minimum os system built then just run 4th from there like via ssh.. might be better than fighting with bear metal. It would bee a bear, too!! 01:10:37 Got a buddy whose big project right now is getting FreeBSD pared down to as few useless dependencies as possible one of the first things you do is go rem out a lot of options in the Generic Kernel, It's not like the FreeBSD kernel is all that big anyhow, really, just for some reason I cant explain, seems to me a Forth should be able to run pretty much 'barefooted' in a pi. But I thionk that ignores a lot of resources that just are not in any 'free 01:10:37 ' forth. and that's supposeing there are some not-free Forths that might have those resources. 01:11:03 I would like there to be Wifi and Ethernet drivers for Forth. 01:11:14 And a TCIP/IP stack, and SSH. 01:11:17 And USB. 01:11:26 But it would be a gigantic pile of work. 01:11:44 yes, it would. big time!! 01:12:11 Paysan's net2o may have TCP/IP done already. 01:12:28 heck even going thru some kind of API to another OS like FreeBSD or linux would be a heavy chore. 01:14:40 crc corrected me on the version of forth that FreeBSD boots from and tho I havent had time yet to research it, it doid mention going back and forth between ficl forth and the FreeBSD kernel in some fashion. 01:15:55 --- join: wa5qjh_1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 01:16:12 really, I've only got some vague idea how that would work, so definiitly not speaking with any authority here just kinda 'spitballin' 01:16:19 --- quit: wa5qjh (Ping timeout: 240 seconds) 01:16:20 --- nick: wa5qjh_1 -> wa5qjh 01:19:49 --- quit: wa5qjh_ (Remote host closed the connection) 01:21:00 --- quit: wa5qjh (Ping timeout: 255 seconds) 01:22:22 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 01:24:03 --- quit: proteusguy (Read error: Connection reset by peer) 01:25:15 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 01:26:27 --- join: proteusguy (~proteus-g@183.89.209.32) joined #forth 01:26:27 --- mode: ChanServ set +v proteusguy 01:26:51 --- quit: wa5qjh (Ping timeout: 255 seconds) 01:26:51 --- nick: wa5qjh_ -> wa5qjh 01:27:01 --- quit: proteusguy (Read error: Connection reset by peer) 01:28:23 --- join: proteusguy (~proteus-g@183.89.209.32) joined #forth 01:28:23 --- mode: ChanServ set +v proteusguy 01:28:40 --- quit: proteusguy (Read error: Connection reset by peer) 01:30:31 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 01:31:20 --- quit: wa5qjh (Ping timeout: 264 seconds) 01:31:23 --- nick: wa5qjh_ -> wa5qjh 01:35:50 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 01:36:08 --- quit: wa5qjh (Ping timeout: 264 seconds) 01:36:08 --- nick: wa5qjh_ -> wa5qjh 01:38:58 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 01:40:56 --- quit: wa5qjh (Ping timeout: 264 seconds) 01:43:03 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 01:44:57 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 01:45:14 --- join: proteusguy (~proteus-g@183.89.209.32) joined #forth 01:45:15 --- mode: ChanServ set +v proteusguy 01:49:03 --- quit: wa5qjh (Ping timeout: 240 seconds) 01:51:17 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 01:54:49 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 01:55:23 --- quit: wa5qjh (Ping timeout: 240 seconds) 01:55:24 --- nick: wa5qjh_ -> wa5qjh 01:59:42 --- quit: wa5qjh (Ping timeout: 255 seconds) 01:59:56 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 02:04:12 --- quit: wa5qjh (Ping timeout: 255 seconds) 02:04:38 --- join: Mat4 (~david@ip5b409eae.dynamic.kabel-deutschland.de) joined #forth 02:05:56 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 02:06:57 Is there a way to run things on the ARC coprocessor embedded in all modern Intel CPUs? 02:07:56 you mean beside ME patches ? 02:08:45 Yes. Your own code. I'd guess not, because that might defeat its purpose. 02:10:30 --- quit: wa5qjh (Ping timeout: 255 seconds) 02:10:51 Sorry, it says on Wikipedia (so it must be true) they use Quark cores now. 02:11:15 Running MINIX 3?!? 02:11:56 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 02:13:24 Theoretical there may be exist a possibility by injecting code at startup misusing the ACPI protocol as command interface. This shouldbe possible independent of the embedded core 02:13:34 (there may exist) 02:14:55 the folks at Positive Technology got code exec on the x86-based ME recently, which they will present at BlackHat Europe this winter 02:16:09 Cool. 02:16:21 --- quit: wa5qjh (Ping timeout: 255 seconds) 02:18:01 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 02:18:22 for AMD processors loading self compiled patches to there ME engine was done before. If you are interested in such things, it is possible a good idea searching for associated publications 02:21:24 anyhow, I do not think programming for these embedded cores is a good idea beside disabling them (which can be done) 02:24:29 (beside with the goal to disable them) 02:25:02 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 02:26:42 --- quit: wa5qjh (Ping timeout: 255 seconds) 02:27:06 --- quit: Mat4 (Quit: leaving) 02:27:53 --- join: Mat4 (~david@ip5b409eae.dynamic.kabel-deutschland.de) joined #forth 02:27:59 --- quit: Mat4 (Client Quit) 02:29:10 --- quit: wa5qjh_ (Ping timeout: 246 seconds) 02:31:26 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 02:35:28 --- quit: wa5qjh (Ping timeout: 246 seconds) 02:37:26 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 02:41:13 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 02:41:46 --- quit: wa5qjh (Ping timeout: 246 seconds) 02:41:48 --- nick: wa5qjh_ -> wa5qjh 02:46:20 --- quit: wa5qjh (Ping timeout: 264 seconds) 02:47:47 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 02:50:50 You are probably right! 02:52:20 --- quit: wa5qjh (Ping timeout: 264 seconds) 02:53:47 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 02:56:41 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 02:58:20 --- quit: wa5qjh (Ping timeout: 264 seconds) 03:00:49 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 03:02:59 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 03:07:19 --- quit: wa5qjh (Ping timeout: 240 seconds) 03:08:59 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 03:11:53 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 03:13:20 --- quit: wa5qjh (Ping timeout: 240 seconds) 03:16:12 --- quit: wa5qjh_ (Ping timeout: 255 seconds) 03:17:52 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 03:22:02 --- quit: wa5qjh (Ping timeout: 255 seconds) 03:23:52 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 03:29:52 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 03:30:09 --- quit: djinni (Quit: Leaving) 03:30:36 --- quit: wa5qjh (Ping timeout: 255 seconds) 03:30:36 --- nick: wa5qjh_ -> wa5qjh 03:33:25 --- join: djinni (~djinni@68.ip-149-56-14.net) joined #forth 03:34:57 --- quit: wa5qjh (Ping timeout: 240 seconds) 03:36:31 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 03:40:27 --- quit: wa5qjh (Ping timeout: 240 seconds) 03:42:40 --- quit: proteusguy (Remote host closed the connection) 04:12:51 --- join: proteusguy (~proteus-g@2405:9800:bc10:1ca:6920:e1c5:f8f6:fa75) joined #forth 04:12:52 --- mode: ChanServ set +v proteusguy 04:57:18 --- quit: nighty- (Quit: Disappears in a puff of smoke) 05:47:12 wa5qjh the 68hc08/HCS08/S08/908? may have more than one manufacturer. I think Freescale took over Motorola's microprocessors. I am not sure how NXP go involved. 05:57:18 I recently bought some Hitachi 6309 microprocessors. They come in a 40-pin DIP and a PLCC. I went in with someone else who was buying a quantity of something like 100 or 200 chips. 05:58:02 6309? or 6809? 05:58:15 6309s 05:58:22 ok, thanks. 05:58:55 https://en.wikipedia.org/wiki/Hitachi_6309 06:02:13 The 6309 is CMOS where the 6809 is P-MOS (or is it N-MOS). So the CMOS can run faster and us less current. 06:02:37 use less current. 06:08:21 --- join: dys (~dys@2a01:598:a084:182f:eab1:fcff:fe36:4b0b) joined #forth 06:17:04 --- join: nighty- (~nighty@s229123.ppp.asahi-net.or.jp) joined #forth 07:28:26 so in the case of ?stack ans forth says if the stack pointer is out of bounds it calls abort 07:28:37 m. out of bounds? on some machines this is not possible 07:29:03 unless you count checking flags for overflow, etc 07:30:14 in the case of some 6502s it doesn't even do that 08:30:40 ANS Forth does not say that. There is no ?STACK in ANS Forth. 08:31:08 But there is an informal agreement on what it does. 08:31:34 It doesn't check on every stack pointer update. 08:33:34 The interpreter calls ?STACK in between each word it encounters. 08:33:51 ok 08:34:05 The usual way to do the check is to compare the stack pointer against the bounding addresses of the stack area. 08:34:42 that make ssense. in starting forth INTERPRET does ?STACK ABORT" Stack Empty" 08:35:11 I'm not quite sure the relation between the two since I'm not sure if stack should be the one calling abort or.. 08:35:40 unless ?STACK is a compiling word or something 08:43:03 --- quit: Zarutian_PI (Read error: Connection reset by peer) 08:43:11 --- join: Zarutian_PI (~3.1415@89.17.133.173) joined #forth 08:45:55 I don't think it is. It's just part of the interpreter. 08:46:12 --- quit: xek (Remote host closed the connection) 08:46:29 --- join: xek (xek@nat/intel/x-ovjcyuzgznszdwru) joined #forth 08:47:39 I'd say ?STACK calls ABORT, but I'm not sure there's a consensus on that. 08:49:30 --- quit: dys (Ping timeout: 240 seconds) 09:07:03 --- join: Mat4 (~david@ip5b409eae.dynamic.kabel-deutschland.de) joined #forth 09:35:44 --- quit: Mat4 (Quit: leaving) 10:49:59 --- join: mnemnion (~mnemnion@2607:fb90:a2bb:c768:d5aa:eaf9:3f1f:6beb) joined #forth 10:53:04 --- join: dys (~dys@46.183.103.8) joined #forth 11:13:30 --- quit: mnemnion (Remote host closed the connection) 11:13:56 --- join: mnemnion (~mnemnion@2607:fb90:a2bb:c768:d5aa:eaf9:3f1f:6beb) joined #forth 11:18:22 --- quit: mnemnion (Ping timeout: 246 seconds) 11:37:19 so to keep things simple, my assembler is only going to support numeric labels 1 through 16 11:37:31 I'm having a hard time settling on the token to use, though 11:38:06 I'd prefer not to use 1: 2: etc. because my convention is that words ending in a colon are defining words 11:38:43 maybe 1# ? 11:40:46 or 1& 12:11:44 ``L1''? 12:37:03 --- quit: dys (Ping timeout: 240 seconds) 13:03:37 oh. that's pretty good 13:47:17 --- join: igstan (~igstan@89.36.15.98) joined #forth 14:13:41 --- quit: igstan (Quit: igstan) 14:31:33 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 14:32:53 --- join: rtmanpages (~rtmanpage@111.sub-174-204-4.myvzw.com) joined #forth 14:36:53 --- join: leaverite (~quassel@175.158.225.198) joined #forth 14:36:53 --- quit: leaverite (Changing host) 14:36:53 --- join: leaverite (~quassel@freebsd/user/wa5qjh) joined #forth 14:39:43 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 14:41:33 --- quit: wa5qjh (Ping timeout: 255 seconds) 14:41:33 --- nick: wa5qjh_ -> wa5qjh 14:46:38 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 14:48:18 --- quit: wa5qjh (Ping timeout: 255 seconds) 14:48:18 --- nick: wa5qjh_ -> wa5qjh 14:53:29 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 14:55:14 --- quit: wa5qjh (Ping timeout: 258 seconds) 14:56:33 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 14:57:55 --- quit: wa5qjh_ (Ping timeout: 258 seconds) 15:00:57 --- quit: wa5qjh (Ping timeout: 240 seconds) 15:02:28 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:06:27 --- quit: wa5qjh (Ping timeout: 240 seconds) 15:08:28 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:12:27 --- quit: wa5qjh (Ping timeout: 240 seconds) 15:14:28 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:18:54 --- quit: wa5qjh (Ping timeout: 255 seconds) 15:19:48 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:24:17 --- quit: wa5qjh (Ping timeout: 255 seconds) 15:26:03 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:28:56 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:30:36 --- quit: wa5qjh (Ping timeout: 255 seconds) 15:33:39 --- quit: wa5qjh_ (Ping timeout: 260 seconds) 15:35:10 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:39:29 --- quit: wa5qjh (Ping timeout: 260 seconds) 15:41:08 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:43:56 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:45:54 --- quit: wa5qjh (Ping timeout: 260 seconds) 15:47:57 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 15:50:10 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:54:27 --- quit: wa5qjh (Ping timeout: 240 seconds) 15:55:05 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:57:53 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 15:59:27 --- quit: wa5qjh (Ping timeout: 240 seconds) 15:59:28 --- nick: wa5qjh_ -> wa5qjh 16:03:08 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 16:03:49 --- quit: wa5qjh (Ping timeout: 240 seconds) 16:03:50 --- nick: wa5qjh_ -> wa5qjh 16:09:09 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 16:10:49 --- quit: wa5qjh (Ping timeout: 240 seconds) 16:13:19 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 16:15:09 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 16:19:06 ... Joe Armstrong is a very smart man. For the longest time I was like wtf is he going on about 16:19:19 --- quit: wa5qjh (Ping timeout: 240 seconds) 16:19:24 but he claimed that APIs are horrible and we should stop making them 16:19:36 But now I realize he was right all along.. 16:20:18 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 16:20:51 --- quit: nighty- (Quit: Disappears in a puff of smoke) 16:24:19 --- quit: wa5qjh (Ping timeout: 240 seconds) 16:26:27 how so 16:26:48 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 16:29:40 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 16:30:19 --- quit: impomatic (Ping timeout: 240 seconds) 16:30:49 --- quit: wa5qjh (Ping timeout: 240 seconds) 16:30:50 --- nick: wa5qjh_ -> wa5qjh 16:31:01 --- join: impomatic (~impomatic@host86-175-96-15.range86-175.btcentralplus.com) joined #forth 16:35:19 --- quit: wa5qjh (Ping timeout: 248 seconds) 16:35:32 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 16:36:06 --- quit: rtmanpages (Remote host closed the connection) 16:39:35 --- quit: wa5qjh (Ping timeout: 248 seconds) 16:42:05 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 16:44:56 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 16:46:31 --- quit: wa5qjh (Ping timeout: 248 seconds) 16:49:03 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 16:50:55 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 16:55:03 --- quit: wa5qjh (Ping timeout: 240 seconds) 16:57:00 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 17:00:45 the answer lies with finite state machines with a type system. very easy to implement tools in Forth, too! 17:00:58 but to really answer- 17:01:13 APIs without hacky patching doesn't know how to actually handle something like this: 17:01:33 fh = open(filename); fh.close() line = fh.readline() 17:01:51 that's just one example, see the typees system says this is ok 17:01:53 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 17:02:04 which is horrible 17:02:39 either A this program will cause really bad problems or b it will hit a wall that says no you can't do that, because somebody hackily implemented something that prevented you from doing something like this 17:02:49 with a finite state machine, you don't have to do that 17:02:56 this also applies to network protocols, too. 17:03:23 --- quit: wa5qjh (Ping timeout: 240 seconds) 17:03:24 --- nick: wa5qjh_ -> wa5qjh 17:03:27 an awesome feature with the FSM is that it can also point fingers in the program and tell which side is to blame 17:03:41 "who messed up" 17:10:26 I'm not following the premise 17:10:53 fh is presumably some data structure that has state 17:11:37 fh.readline() would then enter some error patch because it's already closed 17:12:05 s/patch/path 17:15:08 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 17:16:48 --- quit: wa5qjh (Ping timeout: 255 seconds) 17:19:19 --- quit: wa5qjh_ (Ping timeout: 240 seconds) 17:20:28 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 17:24:50 --- quit: wa5qjh (Ping timeout: 240 seconds) 17:26:28 --- join: wa5qjh (~Thunderbi@freebsd/user/wa5qjh) joined #forth 17:29:18 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 17:30:49 --- quit: wa5qjh (Ping timeout: 240 seconds) 17:30:50 --- nick: wa5qjh_ -> wa5qjh 17:34:28 --- join: wa5qjh_ (~Thunderbi@freebsd/user/wa5qjh) joined #forth 17:35:15 --- quit: wa5qjh (Ping timeout: 255 seconds) 17:35:15 --- nick: wa5qjh_ -> wa5qjh 17:39:45 --- quit: wa5qjh (Ping timeout: 255 seconds) 17:39:48 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 17:41:54 --- nick: leaverite -> wa5qjh 17:44:15 --- quit: leaverite1 (Ping timeout: 255 seconds) 17:45:49 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 17:49:59 --- quit: leaverite (Ping timeout: 248 seconds) 17:50:54 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 17:54:01 --- join: Jookia (~Jookia@gateway/tor-sasl/jookia) joined #forth 17:55:19 --- quit: leaverite (Ping timeout: 248 seconds) 17:56:54 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 17:57:09 How can I make a word that does 'dup IF' named 'AIF'? I've tried various combinations using immediate / postpone but they seem to make pforth fairly unhappy 17:57:25 Most work in the interpreter but not when compiling 18:00:18 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:01:11 --- quit: leaverite (Ping timeout: 248 seconds) 18:01:12 --- nick: leaverite1 -> leaverite 18:04:17 Jookia: machine forths and its descendents have "a non-destructive IF" http://wiki.c2.com/?MachineForth 18:04:53 Nice 18:05:27 --- quit: leaverite (Ping timeout: 240 seconds) 18:05:28 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:09:27 --- quit: leaverite1 (Ping timeout: 240 seconds) 18:11:27 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:13:54 Basically my problem is that I want to make some of my own primitives that wrap existing ones but compile some calls in before them, so AIF is a good example 18:15:27 --- quit: leaverite (Ping timeout: 240 seconds) 18:17:31 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:21:49 --- quit: leaverite (Ping timeout: 240 seconds) 18:23:46 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:27:49 --- quit: leaverite (Ping timeout: 240 seconds) 18:29:51 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:35:09 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:36:19 --- quit: leaverite (Ping timeout: 240 seconds) 18:39:24 --- quit: wa5qjh (Remote host closed the connection) 18:39:44 --- quit: leaverite1 (Ping timeout: 260 seconds) 18:39:48 --- join: wa5qjh (~quassel@175.158.225.198) joined #forth 18:39:48 --- quit: wa5qjh (Changing host) 18:39:48 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 18:41:11 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:45:34 --- quit: leaverite (Ping timeout: 260 seconds) 18:47:13 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:51:17 --- quit: leaverite (Ping timeout: 248 seconds) 18:53:13 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 18:57:41 --- quit: leaverite (Ping timeout: 248 seconds) 18:59:23 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:02:45 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:03:33 --- quit: leaverite (Ping timeout: 248 seconds) 19:03:34 --- nick: leaverite1 -> leaverite 19:07:51 --- quit: leaverite (Ping timeout: 248 seconds) 19:07:55 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:12:07 --- quit: leaverite1 (Ping timeout: 248 seconds) 19:13:54 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:14:20 Jookia, : AIF COMPILE DUP [COMPILE] IF ; ( I think I used those compiles correctly; my forth actually has a single "smart" [postpone] word so I might have remembered them wrong ) 19:16:54 --- join: nighty- (~nighty@kyotolabs.asahinet.com) joined #forth 19:21:03 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:22:15 --- quit: leaverite (Ping timeout: 248 seconds) 19:22:16 --- nick: leaverite1 -> leaverite 19:24:22 zy]x[yz: That works, thanks. Is there some syntax to compile multiple words at once, or if I want to do multiple things before the if at runtime do I just need to put it in another word? 19:26:51 --- quit: leaverite (Ping timeout: 255 seconds) 19:26:53 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:27:27 --- quit: jedb (Ping timeout: 240 seconds) 19:30:46 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:31:21 --- quit: leaverite1 (Ping timeout: 255 seconds) 19:34:50 --- quit: leaverite (Ping timeout: 240 seconds) 19:37:17 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:40:15 --- quit: ZombieChicken (Remote host closed the connection) 19:40:41 --- join: ZombieChicken (~weechat@gateway/tor-sasl/forgottenwizard) joined #forth 19:41:19 --- quit: leaverite (Ping timeout: 240 seconds) 19:43:11 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:43:40 --- quit: MrBismuth (Read error: Connection reset by peer) 19:44:45 --- join: jedb (~jedb@123.100.45.84) joined #forth 19:46:44 --- join: MrBusiness (~ArcMrBism@2602:306:8325:a300:c801:d7f:77e1:92be) joined #forth 19:51:26 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:52:19 --- quit: leaverite (Ping timeout: 240 seconds) 19:52:20 --- nick: leaverite1 -> leaverite 19:57:31 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 19:59:10 --- quit: leaverite (Ping timeout: 255 seconds) 19:59:10 --- nick: leaverite1 -> leaverite 20:02:47 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:03:40 --- quit: leaverite (Ping timeout: 255 seconds) 20:03:40 --- nick: leaverite1 -> leaverite 20:07:57 --- quit: leaverite (Ping timeout: 240 seconds) 20:08:06 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:14:16 zy]x[yz: been writing my papers on forth, but anyways- you shouldn't -have- to write an error patch 20:14:30 with a finate state machine, your state is either perfectly valid, or not valid at all 20:15:11 Is it possible to exit a loop in a function but run code after the loop? :t1 BEGIN LEAVE UNTIL 1 ; doesn't push 1 to the stack 20:15:57 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:17:27 --- quit: leaverite (Ping timeout: 240 seconds) 20:18:45 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:19:57 --- quit: leaverite1 (Ping timeout: 240 seconds) 20:24:01 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:25:17 --- quit: leaverite (Ping timeout: 258 seconds) 20:28:21 --- quit: leaverite1 (Ping timeout: 258 seconds) 20:30:00 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:35:40 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:36:47 --- quit: leaverite (Ping timeout: 258 seconds) 20:40:07 --- quit: leaverite1 (Ping timeout: 248 seconds) 20:41:39 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:45:59 --- quit: leaverite (Ping timeout: 248 seconds) 20:47:54 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:48:08 Hey guys, just found something real interesting. It's the TI "Launchpad". for 20:48:08 everybody, including me, that wants a Forth capable, small single-boad 20:48:08 computer that wont bread the bank and already has wifi on board. No, I dont have one. 20:48:08 And this doesnt answer the questions we had yesterday, but it might give the 20:48:08 chance to try to find an answer, or find some other way to talk to it. 20:48:10 with 256KB of rom, there should be enough space for both TI's drivers and a 20:48:12 pretty good sized Forth. http://www.ti.com/tool/cc3220sf-launchxl ~$50 20:49:32 FatalNIX, I guess my point is that I don't understand the difference between fh and a fsm 20:49:57 or more specifically, what you're referring to as a fsm 20:51:34 oops! sorry, guess that could have been better timed. 20:52:23 --- quit: leaverite (Ping timeout: 248 seconds) 20:52:44 wa5qjh, asynchronous conversations are normal on irc 20:52:56 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 20:53:37 also Jookia, referring to your first question, it's probably best to just put your prefix stuff in a word and COMPILE it 20:54:48 thanks for understanding :) You probably saw my comments yesterday about running forth as the primary OS on an ARm device such as the R-Pi. 20:59:33 --- quit: leaverite (Ping timeout: 255 seconds) 20:59:57 --- quit: wa5qjh (Ping timeout: 240 seconds) 21:02:28 --- join: wa5qjh (~quassel@175.158.225.198) joined #forth 21:02:28 --- quit: wa5qjh (Changing host) 21:02:28 --- join: wa5qjh (~quassel@freebsd/user/wa5qjh) joined #forth 21:05:01 larsb jn_ johnmark here's another launchpad with a whole lot of onboard memory but no wifi stuff 21:05:01 nor as big a price tag ~$13 http://www.ti.com/tool/msp-exp432p401r 21:05:54 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:06:12 --out 21:10:19 --- quit: leaverite (Ping timeout: 240 seconds) 21:11:04 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:15:19 --- quit: leaverite (Ping timeout: 240 seconds) 21:17:41 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:21:02 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:21:49 --- quit: leaverite (Ping timeout: 240 seconds) 21:21:50 --- nick: leaverite1 -> leaverite 21:25:28 : AIF COMPILE dup POSTPONE IP ; IMMEDIATE seems to break in interpret mode :\ 21:26:14 --- quit: leaverite (Ping timeout: 258 seconds) 21:26:17 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:26:50 --- quit: midre (Quit: ZNC - http://znc.in) 21:27:20 --- join: midre (~midre@2601:547:500:2a80:ba27:ebff:fe92:97dd) joined #forth 21:28:38 --- nick: leaverite1 -> leaverite 21:31:27 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:33:08 --- quit: leaverite (Ping timeout: 258 seconds) 21:34:22 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:35:49 --- quit: leaverite1 (Ping timeout: 258 seconds) 21:38:45 --- quit: leaverite (Ping timeout: 248 seconds) 21:39:58 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:44:05 --- quit: leaverite (Ping timeout: 248 seconds) 21:46:17 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:49:45 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:50:29 --- quit: leaverite (Ping timeout: 248 seconds) 21:50:30 --- nick: leaverite1 -> leaverite 21:54:47 --- quit: leaverite (Ping timeout: 248 seconds) 21:54:59 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 21:57:49 wa5qjh that looks like a very good choice to run forth. 21:59:03 --- quit: leaverite (Ping timeout: 248 seconds) 22:01:19 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:03:02 --- part: Jookia left #forth 22:04:08 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:05:27 --- quit: leaverite (Ping timeout: 248 seconds) 22:08:23 --- quit: leaverite1 (Ping timeout: 255 seconds) 22:10:08 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:14:01 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:14:42 --- quit: leaverite (Ping timeout: 255 seconds) 22:14:42 --- nick: leaverite1 -> leaverite 22:18:49 --- quit: leaverite (Ping timeout: 240 seconds) 22:19:10 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:21:59 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:23:19 --- quit: leaverite (Ping timeout: 240 seconds) 22:23:36 --- quit: proteusguy (Remote host closed the connection) 22:25:57 --- quit: leaverite1 (Ping timeout: 240 seconds) 22:27:03 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:31:27 --- quit: leaverite (Ping timeout: 240 seconds) 22:32:58 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:35:50 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:36:57 --- quit: leaverite (Ping timeout: 240 seconds) 22:36:58 --- nick: leaverite1 -> leaverite 22:41:03 --- quit: leaverite (Ping timeout: 240 seconds) 22:41:14 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:45:23 --- quit: leaverite (Ping timeout: 240 seconds) 22:47:14 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:50:10 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 22:51:23 --- quit: leaverite (Ping timeout: 240 seconds) 22:54:24 --- quit: leaverite1 (Ping timeout: 258 seconds) 22:56:06 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:00:32 --- quit: leaverite (Ping timeout: 258 seconds) 23:02:10 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:05:09 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:06:40 --- quit: leaverite (Ping timeout: 258 seconds) 23:09:44 --- quit: leaverite1 (Ping timeout: 264 seconds) 23:11:11 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:11:51 --- quit: jedb (Ping timeout: 255 seconds) 23:12:07 --- join: jedb (~jedb@71.19.249.82) joined #forth 23:16:12 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:18:08 --- quit: leaverite (Ping timeout: 264 seconds) 23:18:08 --- nick: leaverite1 -> leaverite 23:21:16 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:22:56 --- quit: leaverite (Ping timeout: 264 seconds) 23:22:57 --- nick: leaverite1 -> leaverite 23:26:21 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:26:46 --- quit: roundsf (Read error: Connection reset by peer) 23:26:57 --- quit: leaverite (Ping timeout: 240 seconds) 23:26:58 --- nick: leaverite1 -> leaverite 23:31:27 --- quit: leaverite (Ping timeout: 240 seconds) 23:32:20 --- join: roundsf (~user@2a00:2381:1a72:10:fcab:ee24:faf0:748d) joined #forth 23:32:55 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:35:48 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:36:57 --- quit: leaverite (Ping timeout: 240 seconds) 23:36:57 --- nick: leaverite1 -> leaverite 23:41:03 --- quit: leaverite (Ping timeout: 240 seconds) 23:41:22 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:45:23 --- quit: leaverite (Ping timeout: 240 seconds) 23:47:31 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:52:17 --- join: leaverite1 (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:54:09 --- quit: leaverite (Ping timeout: 260 seconds) 23:56:30 --- quit: leaverite1 (Ping timeout: 240 seconds) 23:58:16 --- join: leaverite (~Thunderbi@freebsd/user/wa5qjh) joined #forth 23:59:59 --- log: ended forth/17.10.11