00:00:00 --- log: started forth/19.11.01 01:24:01 --- quit: dddddd (Remote host closed the connection) 01:43:48 --- nick: X-Scale` -> X-Scale 01:47:58 --- join: dys joined #forth 01:49:40 --- quit: jedb_ (Ping timeout: 276 seconds) 02:00:26 --- quit: cartwright (Remote host closed the connection) 02:03:11 --- join: cartwright joined #forth 02:34:57 --- quit: WickedShell (Remote host closed the connection) 02:35:00 --- join: proteus-guy joined #forth 03:39:59 --- quit: proteus-guy (Ping timeout: 265 seconds) 03:49:47 --- join: iyzsong joined #forth 03:51:55 --- join: proteus-guy joined #forth 03:52:43 --- join: jedb_ joined #forth 03:52:57 --- nick: jedb_ -> jedb 03:59:15 --- quit: f-a (Quit: leaving) 05:38:33 --- join: MrMobius joined #forth 06:18:49 --- quit: jdavidbo` (Remote host closed the connection) 06:25:01 --- join: jdavidboyd joined #forth 08:01:04 --- quit: iyzsong (Quit: ZNC 1.7.1 - https://znc.in) 08:12:21 --- quit: tp (Remote host closed the connection) 08:12:25 --- join: tpbsd joined #forth 08:12:25 --- quit: tpbsd (Changing host) 08:12:25 --- join: tpbsd joined #forth 08:45:02 --- join: dddddd joined #forth 09:27:55 --- quit: jdavidboyd (Quit: ERC (IRC client for Emacs 26.3)) 09:29:46 --- join: jdavidboyd joined #forth 09:39:27 --- quit: jdavidboyd (Remote host closed the connection) 09:40:32 --- join: jdavidboyd joined #forth 09:57:45 --- quit: dave0 (Quit: dave's not here) 12:05:22 --- log: started forth/19.11.01 12:05:22 --- join: clog joined #forth 12:05:22 --- topic: 'Forth Programming | 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' 12:05:22 --- topic: set by proteusguy!~proteusgu@cm-58-10-209-120.revip7.asianet.co.th on [Wed Jun 26 09:13:14 2019] 12:05:22 --- names: list (clog jdavidboyd dddddd tpbsd MrMobius jedb proteus-guy cartwright dys gravicappa Keshl_ tabemann +KipIngram X-Scale inode chunkypuffs dave9 pointfree lonjil nonlinear[m] siraben jimt[m] alexshpilkin +proteusguy reepca C-Keen djinni presiden DKordic dzho pareidolia jpsamaroo bluekelp fiddlerwoaroof ornxka APic patrickg dne WilhelmVonWeiner rpcope a3f rann deesix arrdem jn__ remexre yunfan gabc irsol cp +crc diginet2 superjudge alex4nder rprimus phadthai) 12:05:22 --- names: list (nonlinear jhei guan dbucklin Kumool jackdaniel malyn Lord_Nightmare ecraven louisg mstevens catern ovf) 12:13:17 --- join: newcup joined #forth 12:19:26 --- quit: dys (Ping timeout: 245 seconds) 12:22:23 --- join: TonySidaway joined #forth 12:38:15 --- join: WickedShell joined #forth 13:23:37 --- quit: gravicappa (Ping timeout: 240 seconds) 13:46:25 --- quit: inode (Quit: ) 14:38:41 --- join: f-a joined #forth 14:46:21 --- nick: tpbsd -> tp 15:40:52 --- quit: WickedShell (Read error: Connection reset by peer) 15:41:12 --- join: WickedShell joined #forth 17:04:16 --- join: X-Scale` joined #forth 17:05:59 --- quit: X-Scale (Ping timeout: 240 seconds) 17:06:00 --- nick: X-Scale` -> X-Scale 17:51:52 --- quit: cartwright (Remote host closed the connection) 17:58:15 --- join: cartwright joined #forth 18:46:54 * f-a programs a game 18:47:23 some zx spectrum games were made w/ forth, wonder if it feasible to use it to this day 18:48:15 why not ? 18:51:36 well you said you would prefer using a lisp/scheme, right tp ? 18:51:51 I think it's feasible to use Forth for pretty much anything, provided you're ready to do all the coding you'll need to do. 18:52:00 Forth would out-perform Lisp/Scheme. 18:52:39 f-a, I only want to use lisp/scheme on a PC, on all small embedded I'm only using Forth/assembler 18:53:10 solid answer 18:53:38 KipIngram, Forth outperforms everything but assembler and compiled C in my tests 18:53:49 also finished "thinking forth" 18:53:51 very nice book 18:54:41 KipIngram: I could write a small game just to test the water, but gforth ffi are not of my liking 18:54:41 KipIngram, I find that the Forth I use is about 3x slower than compiled C on small embedded, but about 30x faster than ulisp etc 18:55:47 also happy remembrance day everyone 18:56:11 f-a, Thinking Forth is one of my favorites, I have learnt a lot from it and it hasn't finished with me yet 18:56:57 tp: title is wrong though, I mean there are excellent ideas for other programming languages too 18:57:01 for programming in general 18:57:05 and eve project management 18:58:15 f-a, I gues a lot of Forth concepts apply elsewhere 18:58:38 I know my Perl programming benefited greatly from my Forth programming 18:59:16 --- join: iyzsong joined #forth 19:09:34 --- join: rdrop-exit joined #forth 19:15:23 c[] Good morning Forthwrights 19:18:16 morning Zen Master of Forth 19:19:10 Likewise Master Technician 19:26:30 f-a, Thinking Forth is one of my favorite books as well 19:31:21 f-a Yes, my own Forth appears to be about 3x slower than GForth on the (very limited) cases I've explored. 19:31:43 And about 30x times as fast as Python. 19:32:12 KipIngram: is your forth public? 19:34:03 No, not yet. Still have some things I want to do on it. 19:34:17 I may release it, or a large subset of it, at some point. 19:34:21 It's written in nasm. 19:34:30 --- quit: TonySidaway (Quit: TonySidaway) 19:34:35 I'm working now on making it meta-compile capable. 19:34:55 Well, I haven't worked on it for a while - been interested in other things. But that's the next big agenda item. 20:23:45 KipIngram, nasm is probably the best asm for x86. But will your forth have its own asm? 20:27:15 --- quit: f-a (Read error: Connection reset by peer) 20:40:18 --- quit: proteus-guy (Ping timeout: 265 seconds) 21:06:36 --- join: gravicappa joined #forth 21:35:06 --- join: proteus-guy joined #forth 21:38:54 --- quit: X-Scale (Ping timeout: 268 seconds) 21:39:14 --- join: X-Scale` joined #forth 21:39:28 --- join: dave0 joined #forth 21:39:37 --- nick: X-Scale` -> X-Scale 22:24:19 It has a subset assembler currently. 22:25:01 I wrote a code generator that covers the basic, most important instructions. 22:25:41 My strategy is to have some things I call "portable instructions" - they're immediate words that output a few instrutions of machine code to implement some virtual operation. 22:25:55 They were chosen to have efficient implementations on both x86 and ARM. 22:26:05 Then write the primitives in those, and the rest is as usual. 22:26:23 So to port I should just have to write the p.i.'s for the new processor. 22:27:42 If I'd wanted maximum portability I probably could have come up with a dozen or 15 or so p.i.'s that would get the whole job done, but I'm interested in performance, so I wound up with several dozen. 22:28:01 But still better than writing every primitive in per-processor assembly. 22:28:24 I have a lot of primitives in my system, so the layered approach really helps. 22:42:25 --- join: ryke joined #forth 22:48:49 --- quit: bluekelp (Read error: Connection reset by peer) 23:14:33 --- quit: dddddd (Remote host closed the connection) 23:55:43 BTW ulisp is garbage. 23:55:53 Good mornin everyone. 23:56:02 heyho DKordic 23:58:11 DKordic, there is no way I'm using anything but Forth on small embedded, none of the alternatives (i.e. ulisp) will fit into 20KB anyway 23:59:28 I see. What do You think about Lisp in general? 23:59:59 --- log: ended forth/19.11.01