00:00:00 --- log: started forth/19.05.24 00:34:41 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 00:36:55 --- quit: jhei (Ping timeout: 252 seconds) 00:43:48 --- join: jhei (sid81469@gateway/web/irccloud.com/x-eawgorzxtsylpnbt) joined #forth 00:47:13 --- join: rdrop-exit (~markwilli@112.201.166.63) joined #forth 01:06:09 These embeddable C Forth-ishes are cool and all but like 01:06:33 the new wave of Forth derivatives needs more compilers 01:06:46 compile-time being "put into the binary" time 01:09:22 --- quit: jhei (Ping timeout: 252 seconds) 01:11:27 --- join: jhei (sid81469@gateway/web/irccloud.com/x-zvudhkgcbhamennw) joined #forth 01:19:03 --- quit: tabemann (Ping timeout: 250 seconds) 01:20:55 --- join: tabemann (~tabemann@2600:1700:7990:24e0:b944:a349:56b9:12fb) joined #forth 02:04:18 --- join: dave0 (~dave0@069.d.003.ncl.iprimus.net.au) joined #forth 02:04:34 --- quit: ashirase (Ping timeout: 258 seconds) 02:06:37 re 02:06:55 --- join: ashirase (~ashirase@modemcable098.166-22-96.mc.videotron.ca) joined #forth 02:15:14 --- quit: chunkypuffs (Remote host closed the connection) 02:16:22 --- join: chunkypuffs (~chunkypuf@2a01:4f9:2b:16d5::1) joined #forth 03:48:03 --- join: proteusguy (~proteusgu@cm-58-10-208-38.revip7.asianet.co.th) joined #forth 03:48:04 --- mode: ChanServ set +v proteusguy 04:49:09 --- quit: phadthai (Ping timeout: 245 seconds) 04:51:11 --- join: phadthai (mmondor@ginseng.pulsar-zone.net) joined #forth 05:02:58 --- join: xek (~xek@apn-31-0-23-81.dynamic.gprs.plus.pl) joined #forth 05:16:42 --- join: gravicappa (~gravicapp@h178-129-21-185.dyn.bashtel.ru) joined #forth 05:43:00 --- quit: john_metcalf (Quit: http://corewar.co.uk) 06:40:48 --- join: mtsd (~mtsd@94-137-100-130.customers.ownit.se) joined #forth 07:13:24 --- quit: mtsd (Quit: leaving) 07:34:22 --- quit: tabemann (Ping timeout: 252 seconds) 07:53:28 in an Forth-esque dual stack machine ISA I am designing, I am debating with myself having instruction 0x0001 mean LIT_1 just so I can shrink the TOS register MUX from 16 input to 8 input 08:03:49 nope it is going to complicate other parts such as the microcode rom 08:18:16 --- quit: muzgo (Quit: leaving) 08:47:28 --- quit: rdrop-exit (Quit: Lost terminal) 09:00:17 --- join: cnidario (~aaa@92.57.58.87) joined #forth 09:41:38 --- quit: dave0 (Quit: dave's not here) 10:32:55 --- quit: cnidario (Remote host closed the connection) 11:47:29 --- quit: xek (Ping timeout: 245 seconds) 11:48:57 --- join: xek (~xek@apn-31-0-23-81.dynamic.gprs.plus.pl) joined #forth 11:54:13 --- join: xek_ (~xek@apn-37-248-138-202.dynamic.gprs.plus.pl) joined #forth 11:54:34 --- quit: xek (Ping timeout: 245 seconds) 12:01:10 --- quit: gravicappa (Ping timeout: 272 seconds) 12:11:44 --- join: xek__ (~xek@apn-37-248-138-202.dynamic.gprs.plus.pl) joined #forth 12:14:28 --- quit: xek_ (Ping timeout: 272 seconds) 13:16:28 --- quit: Keshl (Ping timeout: 252 seconds) 14:31:54 --- quit: xek__ (Ping timeout: 272 seconds) 15:53:02 --- join: dave0 (~dave0@069.d.003.ncl.iprimus.net.au) joined #forth 15:53:15 hi 15:55:21 dave0: hi 15:55:49 hi remexre 16:06:26 what would you call the number which represents a fixed-point 1? 16:06:47 e.g., if you're working with 16.16 what would you call the constant with the value 65536 16:07:09 1.0 i guess? 16:08:53 is there like an industry conventional descriptive name for the fixed-point unit value, though? 16:09:11 oh don't know :-( 16:09:47 i guess for now i'll just call it unit until i come across something better 17:01:58 --- quit: john_cephalopoda (Ping timeout: 252 seconds) 17:15:32 --- join: john_cephalopoda (~john@unaffiliated/john-cephalopoda/x-6407167) joined #forth 17:20:42 --- join: rdrop-exit (~markwilli@112.201.166.63) joined #forth 17:21:09 c[_] Top of the morning Forthers 17:22:45 zy]x[yz: scaling factor? 17:25:05 maybe 17:25:07 thanks 17:25:14 np 18:42:43 Does anyone have a good way to factor this? https://github.com/siraben/meta-yacc/blob/b032511142cd883b22f339074012c47b48ac37be/meta.fs#L40-L48 18:42:46 It works, but I feel like there's no need to juggle the stack that much to check if a character is whitespace 18:42:59 --- quit: dddddd (Remote host closed the connection) 18:58:19 bl over = over tab = or swap lf = or 18:59:47 There are other whitespace characters than these though 19:02:41 Other alternatives would be early exits on after each test 19:02:55 What other whitespace characterss? 19:03:05 I'm just thinking about ASCII ones 19:03:24 form-feed vertical-tab 19:03:51 carriage return 19:04:14 bl is not a carriage return? 19:04:48 bl is space, i.e. ASCII 32 19:05:04 oops brain fart 19:05:17 lf isn't defined in gforth it seems 19:05:48 it's probably your \n 19:06:17 they use the C language escape code I guess 19:06:40 I see. 19:06:40 In C \f is form feed 19:06:50 \r is carriage return 19:07:45 IIRC \n depends on the OS 19:08:35 or maybe it's just linefeed 19:08:49 \v is vertical tab 19:08:52 just a sec... 19:08:59 https://en.wikipedia.org/wiki/Escape_sequences_in_C 19:09:25 or, you could just do 'man ascii' 19:10:21 If you're using anything other than 7-bit ASCII there might be other whitespace characters to contend with 19:11:20 e.g. Unicode 19:11:29 https://en.wikipedia.org/wiki/Whitespace_character 19:13:42 It all depends on what definition of whitespace is actually relevant to your need 19:15:22 Do you really need a "Mongolian Vowel Separator" :-))) 19:16:29 PoppaVic: Didn't know about "man ascii"! 19:16:56 There's also man unicode it seems 19:23:38 Unicode is messy 19:25:50 --- join: Keshl (~Purple@207.44.70.214.res-cmts.gld.ptd.net) joined #forth 19:26:00 How else to deal with hundreds of different human scripts 19:26:35 C classifies $ 09..0d and $ 20 as whitespace characters 19:27:39 and $7f, I am sure 19:27:51 No, that's delete 19:28:20 C isn't going to care - it's gotta' be same group as \r\n\b 19:28:22 ht lf vt ff cr sp 19:28:45 (I speak of the input stream here) 19:29:13 I'm speaking of C's isspace() function 19:29:21 ah 19:30:47 or in C speak: \t \n \v \f \r and ' ' 19:42:29 dup $ 09 $ 0d between swap bl = or 19:45:21 or if hex is not to your liking: 19:45:39 dup 9 13 between swap bl = or 19:46:37 Assuming ASCII or a superset 19:53:21 siraben: Regarding the hundreds of human scripts. I satisfy myself with ASCII for programming systems/languages, anything beyond ASCII is application level. 19:55:53 rdrop-exit: of course. 19:56:41 The only exceptions for me were EBCDIC on mainframes and APL 19:57:45 Oh and Commodore's PETSCII :) 20:05:40 --- join: gravicappa (~gravicapp@h178-129-21-185.dyn.bashtel.ru) joined #forth 20:08:00 but if you use unicode, you can call divide ÷ ! 20:08:48 lets see C do that :-p 20:13:12 True, Unicode gives some really nice naming opportunities, especially for math related words, reminiscent of APL. 20:13:35 But typing those in would be problematic. 20:14:24 Only a tablet-lover would enjoy it 20:14:55 You could have a system that has two names for each definition, an plain ASCII one, and a "display name". 20:14:59 'course, now yer scrolling yer damned KBD app more than the damned document 20:18:25 You could type in something like "subset" and it would convert the display to the subset character 20:20:22 But I'm too attached to plain old ASCII 20:21:40 and small keyboards 20:29:46 --- join: tabemann (~tabemann@2600:1700:7990:24e0:b944:a349:56b9:12fb) joined #forth 20:45:18 --- quit: dave0 (Quit: dave's not here) 22:19:46 --- quit: rdrop-exit (Quit: Lost terminal) 23:31:02 --- quit: gravicappa (Ping timeout: 258 seconds) 23:59:59 --- log: ended forth/19.05.24