00:00:00 --- log: started forth/19.10.25 00:56:13 --- join: dys joined #forth 01:16:08 --- quit: WickedShell (Remote host closed the connection) 02:19:34 --- join: xek_ joined #forth 02:43:56 if you're looking for exercises to implement in any language, I started collecting sites that do riddles or exercises on different topics: bioinformatics http://rosalind.info/, maths https://projecteuler.net/, cryptography https://cryptopals.com/, random riddles https://adventofcode.com/ (check the various past years) 02:54:37 --- quit: gravicappa (Ping timeout: 265 seconds) 02:55:06 patrickg: the number of such sites has been increasing rapidly as competitive programming gathers more people from around the world. 02:56:16 patrickg: vjudge lists some of those sites on the landing page -> https://vjudge.net/ 03:01:58 I find my Forth code for every hardware device I build has at least 99 problems 03:02:55 --- join: X-Scale` joined #forth 03:03:19 --- quit: X-Scale (Ping timeout: 240 seconds) 03:04:03 --- nick: X-Scale` -> X-Scale 03:12:19 --- quit: Keshl (Read error: Connection reset by peer) 03:12:34 --- join: Keshl joined #forth 03:17:21 --- join: iyzsong joined #forth 03:17:51 X-Scale: thanks for the pointer, but as you say, that's competitive stuff. might serve for ideas (but so does the codegolf reddit/stackoverflow/...), but those tend to be less about learning and more about showing off. 03:22:20 --- join: iyzsong-x joined #forth 03:23:37 --- quit: iyzsong (Ping timeout: 265 seconds) 05:50:23 --- quit: dave0 (Quit: dave's not here) 06:44:52 --- join: warriors joined #forth 06:47:49 --- join: punkbrwstr2 joined #forth 06:49:43 --- join: dddddd joined #forth 07:02:47 --- nick: punkbrwstr2 -> punkbrwstr 07:05:06 --- quit: iyzsong-x (Quit: ZNC 1.7.1 - https://znc.in) 07:06:39 --- quit: punkbrwstr (Quit: leaving) 07:14:52 --- quit: rdrop-exit (Quit: Lost terminal) 07:35:33 --- join: creat1001 joined #forth 07:35:33 --- quit: druffer (Quit: Leaving) 08:00:07 --- nick: ornxka -> notabotiswear 08:00:43 --- nick: notabotiswear -> normalcomputerus 08:01:15 --- nick: normalcomputerus -> ornxka 08:04:11 --- join: xek__ joined #forth 08:07:19 --- quit: xek_ (Ping timeout: 240 seconds) 08:19:48 --- quit: creat1001 (Remote host closed the connection) 08:23:30 --- join: gravicappa joined #forth 08:57:16 --- join: xek_ joined #forth 09:00:01 --- quit: xek__ (Ping timeout: 265 seconds) 09:53:14 --- quit: dys (Ping timeout: 264 seconds) 10:33:19 --- quit: gravicappa (Ping timeout: 240 seconds) 10:35:44 --- quit: xek_ (Remote host closed the connection) 10:36:08 --- join: xek_ joined #forth 10:39:59 --- join: gravicappa joined #forth 12:05:44 --- quit: xek_ (Remote host closed the connection) 12:06:06 --- join: xek_ joined #forth 12:38:54 --- join: WickedShell joined #forth 12:49:13 --- quit: gravicappa (Ping timeout: 240 seconds) 13:18:03 --- join: f-a joined #forth 13:18:21 is there a library for testing forth words 13:18:34 or do you folks just debug by hand and call it a day? 13:28:24 I've seen a library for testing expected behaviour of new Words somewhere and it's used here and there 13:28:43 good to know, got any link? 13:29:00 racking my brains trying to recall where it was atm 13:30:15 --- join: ryke joined #forth 13:43:37 --- quit: warriors (Quit: Connection closed for inactivity) 14:01:32 f-a, I can't find it, whats annoying is I've seen it used recently to test suite of words. I saw it first on github or sourceforge a while ago 14:02:08 tp: thanks for searching! 14:02:20 I will take a stab at github or sourceforge too 14:02:40 I mean it seems something sensible programmers would use 14:03:00 * f-a is also looking at : within2 ( n lo hi+1 -- flag ) over - >r - r> u< ; 14:03:09 I took too long to understand that u< trick! 14:10:33 u< ( u1 u2 - - flag ) u1 less-than u2 ? 14:11:37 I'm pretty sure that the testing stuff is written by one of the active German forthers 14:12:21 tp: within checks boundaries but has only one logic operator 14:12:25 clever definition 14:13:18 using u< is funny 14:14:17 f-a: the hayes testing stuff might be useful 14:14:20 https://github.com/larsbrinkhoff/lbForth/tree/master/test/hayes 14:14:34 the main code is in tester.fth iirc 14:16:55 crc, thanks! thats what I was trying to recall 14:17:50 I have a testing thing for my forth, though it's not as nice as I'd like (so far): http://forth.works/live/tests/test-core.forth 14:17:58 awesome! 14:19:23 f-a, have you read "thinking forth" ? 14:20:06 tp: I am ploughing through the problems as now 14:20:20 that "within" definition came from there 14:20:51 f-a, aha, cool 14:24:26 --- quit: f-a (Quit: leaving) 14:25:33 --- join: f-a joined #forth 14:31:04 --- quit: ryke (Quit: ryke) 14:31:26 --- join: ryke joined #forth 14:35:37 --- quit: f-a (Ping timeout: 240 seconds) 14:37:40 --- join: f-a joined #forth 14:41:44 --- quit: xek_ (Remote host closed the connection) 14:43:00 --- join: xek joined #forth 14:45:47 I should read other people's code more, very interesting testing words indeed 15:29:25 --- quit: ryke (Ping timeout: 245 seconds) 15:40:13 --- join: rdrop-exit joined #forth 15:41:01 --- join: dave0 joined #forth 16:38:45 --- join: ryke joined #forth 17:14:59 --- quit: xek (Ping timeout: 240 seconds) 18:15:46 --- join: druffer joined #forth 18:49:22 --- quit: f-a (Quit: leaving) 18:49:43 --- join: lisbeths joined #forth 19:18:13 --- quit: dave0 (Quit: dave's not here) 19:35:17 --- quit: lisbeths (Remote host closed the connection) 20:22:24 --- quit: ryke (Ping timeout: 268 seconds) 20:38:40 --- join: iyzsong joined #forth 21:33:21 --- join: gravicappa joined #forth 22:24:30 --- quit: gravicappa (Ping timeout: 268 seconds) 22:25:32 --- quit: WickedShell (Remote host closed the connection) 22:56:26 --- quit: dddddd (Remote host closed the connection) 23:12:02 --- join: ryke joined #forth 23:42:18 --- join: f-a joined #forth 23:59:59 --- log: ended forth/19.10.25