00:00:00 --- log: started forth/21.04.06 00:11:26 --- join: f-a joined #forth 00:13:22 --- join: f-a_ joined #forth 00:13:31 --- quit: f-a (Client Quit) 00:19:45 --- quit: f-a_ (Read error: Connection reset by peer) 00:23:37 --- join: xek joined #forth 00:24:01 --- join: f-a joined #forth 00:27:02 --- quit: f-a (Read error: Connection reset by peer) 00:30:01 --- join: f-a joined #forth 00:47:40 --- join: swineflu joined #forth 02:53:05 --- quit: clog (^C) 02:53:05 --- log: stopped forth/21.04.06 02:53:14 --- log: started forth/21.04.06 02:53:14 --- join: clog joined #forth 02:53:14 --- topic: 'Forth Programming | do drop >in | logged by clog at http://bit.ly/91toWN backup at http://forthworks.com/forth/irc-logs/ | If you have two (or more) stacks and speak RPN then you're welcome here! | https://github.com/mark4th' 02:53:14 --- topic: set by mark4!~mark4@cpe-75-191-74-68.triad.res.rr.com on [Sun Feb 28 11:55:01 2021] 02:53:14 --- names: list (clog proteus-guy swineflu xek +proteusguy gravicappa shmorgle boru lispmacs[work] djinni _whitelogger APic jess cantstanya mark4 nitrix @crc rpcope cmtptr ovf dnm veltas rprimus dys X-Scale tabemann Lord_Nightmare jedb MrMobius cp- spoofer pareidolia joe9 Vedran rixard nihilazo Keshl klys crest_ Kumool jimt[m] siraben jyf ecraven xybre bluekelp phadthai rann lonjil krjt mstevens a3f jn__ fiddlerwoaroof +KipIngram kiedtl tolja mjl koisoke_ neuro_sys dzho) 02:53:14 --- names: list (TangentDelta remexre guan ornxka) 04:08:35 --- join: tech_exorcist joined #forth 05:41:01 --- join: f-a joined #forth 06:02:16 This is interesting: https://github.com/s-macke/VoxelSpace 06:02:42 Also they reverse-engineered a Forth game but that's less good because they converted it to C https://github.com/s-macke/starflight-reverse 06:06:21 veltas, I think you're getting to the root of the problem re assemblers 06:07:22 why use forth? 1. youre on an extremely constrained system, 2. you could be doing it in any other language, 3. it's a toy/hobby/for fun 06:08:00 if its 2 then why use forth for this? if its 3, then go for it and use a janky syntax 06:08:02 --- quit: tech_exorcist (Remote host closed the connection) 06:08:14 And if it's 1 use an existing assembler? 06:08:22 --- join: tech_exorcist joined #forth 06:08:45 as long as youre only writing it for fun or only going to assembly a few test or demo programs with it then it doesnt matter if the syntax is weird or non ideal 06:08:48 It is quite powerful being able to assemble code in your Forth though 06:08:59 --- quit: tech_exorcist (Remote host closed the connection) 06:09:19 --- join: tech_exorcist joined #forth 06:09:20 --- quit: tech_exorcist (Remote host closed the connection) 06:09:39 it is powerful but that's different than writing thousands of lines into an assembly file and assembling that which is where you would want 2 06:09:53 which also has the advantage of being able to assemble other people's files 06:20:36 If you all wanna see the first public beta test of our new platform this coming Thursday (8p BKK GMT+7) check out this Fb event: https://www.facebook.com/events/209019941016891 06:28:39 --- join: lchvdlch joined #forth 06:33:20 --- join: tech_exorcist joined #forth 06:33:52 --- quit: tech_exorcist (Remote host closed the connection) 06:34:12 --- join: tech_exorcist joined #forth 06:34:12 --- quit: tech_exorcist (Remote host closed the connection) 06:36:51 --- join: tech_exorcist joined #forth 06:38:40 --- join: wineroots joined #forth 06:41:23 --- quit: f-a (Quit: leaving) 07:21:41 proteusguy: What kind of platform is this? I'm trying to fit togher "product" and "rock band" in my head. 07:24:58 KipIngram, easier to show than tell I think... ;-) https://drive.google.com/file/d/1G2oJmEkLXj7I8FzVTaTtsNhkbf2K1lNP/view?usp=sharing 07:26:15 This video shows our platform compared to the two "leading" platforms. ;-) 07:29:56 --- join: f-a joined #forth 07:40:02 Showing works - only took a few seconds to understand. That's cool. 07:43:30 Got a more direct link to the YouTube event now... https://www.youtube.com/watch?v=LDZFybcPnco 07:50:43 https://sun9-17.userapi.com/impg/R92P2ajgO4tJVSauSMidW_Xeyxo4XvCMAS1y_g/YpnOe51EhcU.jpg?size=1620x2160&quality=96&sign=9e0999d274f05c33b12320f736e332b9&type=album 07:50:55 (my friend’s) 07:55:37 +1 not even sure how many time's I've read that book by now... still have my original copy! 07:56:36 :-) I've got an original copy of it somewhere upstairs. 07:56:38 Also. 07:59:52 --- join: f-a_ joined #forth 08:00:21 --- quit: f-a (Ping timeout: 260 seconds) 08:01:40 --- quit: f-a_ (Client Quit) 08:01:56 --- join: f-a joined #forth 08:03:23 Here's mine. And the torn paper was my bookmark with a list of local BBS' in Forth Smith, Arkansas. This would be circa-1984-86. https://ibb.co/HP74nHN 08:03:48 Note the modem settings for 300 & 1200 baud... ;-) 08:08:40 --- quit: f-a (Ping timeout: 240 seconds) 08:10:42 --- join: f-a joined #forth 08:17:01 f-a: Nice 08:17:05 And nice kitty 08:18:18 I'm assuming that's a print-out rather than the original print? 08:18:25 I seem to remember the original was in a blue cover 08:19:00 print out 08:19:07 I think he printed it on a needle printer 08:19:21 An older gent at my office has a copy of Starting FORTH, which he almost gave to me before realising it might be worth something 08:19:28 No idea though, probably not worth too much right? 08:19:41 probably not 08:19:50 my father had a first edition but it got runed in a flood 08:19:58 It's valuable to the right buyer but how to set that up? It's the sort of thing that could auction on ebay for £10 08:20:00 yeah do not think there is a market for Fort memorabilia xD 08:21:44 There's a couple on UK eBay right now, one is buy-it-now for £35, other is auction with no bids asking £30 08:23:11 It feels like Forth activity has spiked in the time I've known Forth, maybe they'll become valuable later? 08:23:27 Nobody will truly appreciate Forth until all the older Forthers are long gone probably :P 08:23:54 fuck people amassing stuff for ebay 08:30:02 Well that can go both ways, end up buying stuff that loses value 08:32:20 a part of me hopes so :P 08:34:19 --- quit: tech_exorcist (Ping timeout: 265 seconds) 08:34:20 Also their push to buy up old stuff to sell it on ebay means they will likely preserve it better than people who simply don't care about their old stuff and are trying to get rid of it or will just let their family throw it all out when they die 08:34:44 So it might help increase the amount of preserved older tech/books 08:36:54 resellers are a pain in many other markets 08:37:01 e.g. I like fountain pens 08:37:05 stopped w/ those 08:39:37 b/c resellers 08:39:53 I will stop complaining, at least we have an online copy 08:55:43 --- quit: f-a (Quit: leaving) 09:32:23 --- join: f-a joined #forth 10:45:18 --- quit: gravicappa (Ping timeout: 265 seconds) 10:46:57 --- join: gravicappa joined #forth 11:56:37 Well, I added a snapshot / recover snapshot phrase immediately after WARM. The snapshot is there just so the recover operation will have something to recover - the recover operation right there is the re-entry point after error handling. The snapshot word stashes the data stack pointer in a variable before making the image - the recover operation uses it to reset the data stack. 11:56:45 After that recovery we have QUIT. 11:57:06 And then QUIT calls SNAP just before running INTERPRET. 11:57:32 I found that arrangement to be fully bulletproof error recovery last time. 11:58:17 Basically if a INTERPRET detects an error of any kind, the whole line is ignored. 12:04:36 I suppose obviously a really bad glitch could corrupt the snapshot, or the roadmap to it, but other than that... 12:08:40 --- quit: f-a (Read error: Connection reset by peer) 12:10:33 --- join: tech_exorcist joined #forth 12:13:37 --- join: f-a joined #forth 13:10:39 --- quit: tech_exorcist (Quit: tech_exorcist) 13:10:55 --- join: tech_exorcist joined #forth 13:11:45 --- quit: gravicappa (Ping timeout: 265 seconds) 13:16:11 --- nick: jess -> j 13:26:21 --- quit: f-a (Quit: leaving) 13:42:50 --- quit: xek (Quit: Leaving) 15:32:14 --- quit: tech_exorcist (Remote host closed the connection) 17:01:39 --- quit: wineroots (Remote host closed the connection) 17:19:40 --- quit: joe9 (Ping timeout: 240 seconds) 17:21:56 --- join: joe9 joined #forth 17:34:02 --- join: dave0 joined #forth 17:35:21 maw 17:51:47 --- join: wineroots joined #forth 18:25:17 Hey dave0. 18:27:37 hi KipIngram 18:39:24 --- join: boru` joined #forth 18:39:26 --- quit: boru (Disconnected by services) 18:39:29 --- nick: boru` -> boru 20:24:05 --- quit: joe9 (Ping timeout: 268 seconds) 20:27:17 --- join: joe9 joined #forth 20:30:58 --- quit: dave0 (Quit: dave's not here) 20:31:28 --- quit: joe9 (Ping timeout: 240 seconds) 20:33:42 --- join: joe9 joined #forth 21:18:00 --- quit: joe9 (Ping timeout: 240 seconds) 21:20:15 --- join: joe9 joined #forth 21:21:57 veltas, I agree forth activity has clearly exploded. Stackbased VMs have always been a thing but crypto systems are definitely growing and share the limited resource and focus on simplicity that is natural to forth. The crypto-world stands to gain tremendously from the experience of forth-wrights. 21:55:07 --- join: gravicappa joined #forth 22:07:50 --- join: dave0 joined #forth 22:08:14 maw 23:28:06 --- join: f-a joined #forth 23:37:48 --- quit: f-a (Ping timeout: 240 seconds) 23:39:54 --- join: f-a joined #forth 23:45:20 --- quit: f-a (Ping timeout: 240 seconds) 23:47:34 --- join: f-a joined #forth 23:52:13 --- quit: f-a (Read error: Connection reset by peer) 23:55:18 --- join: f-a joined #forth 23:59:59 --- log: ended forth/21.04.06