00:00:00 --- log: started forth/19.08.19 00:03:49 --- join: dys (~dys@2003:5b:203b:100:a64c:c8ff:fef4:13a6) joined #forth 00:47:23 --- join: nullnullnull (~no@bzq-79-179-76-17.red.bezeqint.net) joined #forth 01:05:37 morning forth 01:06:05 gday WilhelmVonWeiner 01:10:41 complexity sucks 01:11:06 there are so many layers of abstraction between my javascript SIP library and the phone 01:11:13 that debugging is a massive pain 01:11:20 eww, nasty 01:11:47 I only hate debugging when I don't have the tools I need 01:12:20 which is why I spent so long building my Forth embedded development system as I learnt the language 03:03:08 guys, how to exit(1) with gforth? (it's not working for me with C code) 03:03:46 I can upload my script if needed 03:34:36 --- join: dddddd (~dddddd@unaffiliated/dddddd) joined #forth 03:43:55 throw? 03:46:23 I think ciforth has exit codes 03:46:47 http://home.hccnet.nl/a.w.m.van.der.horst/ci86.lina.html#EXIT-CODE 03:46:55 gforth is actually cance 04:06:13 hmm 04:21:05 Don't use gforth, can't help you there. 04:30:54 The developers of gForth hang out on comp.lang.forth 04:33:12 along with a few trolls and general nut jobs ... 04:34:15 comp.lang.forth isn't the friendly and polite Forth club this channel is :) 04:34:43 whole usenet is hardly on the same planet as friendly and/or polite 04:35:22 on the positive side Elisabeth D Rather and Stephen Pelc are likely to read your posts and reply :) 04:35:31 jackdaniel, so true 04:37:19 True, this channel is very civil compared to clf 04:40:43 because c.l.f is so antagonistic in nature and so programmer Forth language focused, I don't bother reading it any more as Im a Forth user, not a programmer 04:41:50 there are two types of Forth people, the first type spend their lives discussing the language and writing Forths, the second type (like me) just use Forth in our embedded projects 04:42:37 Id start a club, but there are only 42 of us world wide, and I only know 2 or 3 of them ;-) 04:54:13 --- join: dave0 (~dave0@069.d.003.ncl.iprimus.net.au) joined #forth 04:57:32 You have a third type, that like Chuck alternates between making, using, and continuously refining their own custom Forth tools. There's nothing quite like using tools you understand and control at every level, and that are perfectly adapted to your way of thinking and working. 04:57:53 ah yes, of course 04:59:27 I make my own tools, just not my own Forth. I agree Id be much more capable if I did write my own Forth but Im comfortable just being a Forth user 05:13:43 I think if you had deep dived into Forth a couple decades earlier, you would probably have at some point switched to your own Forth. It's often a natural next step in a Forther's evolution, after years of using Forth. Admittedly it can be counter-productive for an over-confident newbie who hasn't yet grokked Forth but thinks they can build a better mousetrap right off the bat. 05:14:33 wise words, I hadn't thought of that :) 05:16:26 :) 05:18:06 Dinner time, catch you later, keep on Forthin' :) 05:18:28 cya! 05:18:35 --- quit: rdrop-exit (Quit: Lost terminal) 08:47:08 --- quit: dave0 (Quit: dave's not here) 09:18:26 --- quit: dys (Ping timeout: 264 seconds) 09:32:53 --- join: dys (~dys@tmo-087-39.customers.d1-online.com) joined #forth 10:07:39 --- join: wildtrees (~wildtrees@unaffiliated/wildtrees) joined #forth 10:09:53 --- quit: wildtrees (Max SendQ exceeded) 11:26:56 --- join: mtsd (~mtsd@94-137-100-130.customers.ownit.se) joined #forth 12:17:44 --- quit: louisg (Ping timeout: 246 seconds) 12:17:45 --- quit: gravicappa (Ping timeout: 248 seconds) 12:17:46 --- quit: remexre (Ping timeout: 248 seconds) 12:35:45 --- join: louisg (~louis@x-160-94-179-187.acm.umn.edu) joined #forth 12:38:30 --- quit: mtsd (Quit: Leaving) 12:42:50 --- join: remexre (~nathan@x-160-94-179-186.acm.umn.edu) joined #forth 14:34:14 --- quit: dys (Ping timeout: 246 seconds) 14:38:54 --- join: ryke (~Thunderbi@71-9-169-152.dhcp.jcsn.tn.charter.com) joined #forth 14:47:07 nullnullnull: Do you mean `bye`? 14:50:04 Hm `bye` has status code 0 14:50:31 nullnullnull: as far as I can see from the gforth manual, the only way I see to do exit(1) is via the c interface 14:53:02 nullnullnull: `: exit(1) ( -- ) 1 (bye) ;` 14:56:12 <`presiden> so, (bye) not bye 14:56:26 <`presiden> ah, yes 14:56:30 <`presiden> can confirm 14:57:19 * crc dislikes undocumented words 14:57:22 * pointfree has been designing a blank-slate characterset http://ix.io/1SLK and is looking for preferences and opinions on pixel fonts. 14:59:22 I just searched the gforth source code and found that `bye` is defined as `: bye 0 (bye) ;` I guess `(bye)` is supposed to be internal given the naming scheme. 15:05:35 In my block editor cad tool I define colored character glyphs for metal1, metal2, ndiff, pdiff, polysilicon. Instead of bytes I have xt's in the lookup table and `execute` them as soon as they are typed. 15:06:36 A drcs sixel character glyph is just two rows of sixels separated by a / 15:08:24 I like the idea of doing a hexdump with just `( addr n --) type` 15:46:50 --- quit: nullnullnull (Ping timeout: 248 seconds) 16:25:01 --- quit: john_cephalopoda (Ping timeout: 264 seconds) 16:37:54 --- join: john_cephalopoda (~john@unaffiliated/john-cephalopoda/x-6407167) joined #forth 16:46:22 --- join: farcas82regreg (~regreg@2a02:2f01:8702:7000:ac93:c643:d0f1:8578) joined #forth 16:51:50 --- quit: MrMobius (Ping timeout: 258 seconds) 18:57:31 --- join: MrMobius (~default@c-73-134-82-217.hsd1.va.comcast.net) joined #forth 19:48:58 --- join: tabemann (~tabemann@2600:1700:7990:24e0:e806:660e:3766:21c9) joined #forth 19:49:10 --- join: PoppaVic (~PoppaVic@unaffiliated/poppavic) joined #forth 20:15:45 --- part: PoppaVic left #forth 20:16:22 --- join: nullnullnull (~no@bzq-79-179-76-17.red.bezeqint.net) joined #forth 20:16:54 pointfree, sry I'm back, I will try "bye" command 20:17:35 so bye and 1 bye? 20:18:07 1 (bye) 20:19:12 it's working but now I have another problem :P 20:19:26 sec I will upload my code to explain 20:20:12 https://pastebin.com/0py1ittF 20:20:34 the "bye" is working but the tasks are not running in parallel 20:20:52 I mean, I want to run the script for 2sec and stop with failure 20:21:16 but if the script successfully executed one of the tasks: it should stop immediately 20:21:22 (task2) 20:21:40 I'm trying to do a "timeout" connection there 20:21:49 max-timeout 2 sec, if failed then stop 20:21:54 for socket connection 20:22:28 but seems like, the tasks are not really running in parallel 20:23:50 check for example about timeout: google.com port:1234 20:53:27 --- quit: farcas82regreg (Ping timeout: 252 seconds) 20:56:29 --- join: gravicappa (~gravicapp@h109-187-16-242.dyn.bashtel.ru) joined #forth 20:59:30 --- quit: dddddd (Remote host closed the connection) 21:24:00 (1) there's nothing in the paste that actually creates tasks 21:25:27 (2) tasker.fs appears to be cooperative; I'm not sure it'll work for this 21:27:11 hmm, I need to create that task dynamically? 21:27:28 I wrote the tasks there and just called them from main 21:27:31 I don't know 21:27:52 like a function 21:28:04 but not sure if it's the correct way 21:28:15 you are calling the *words*, not creating a task loop 21:28:33 btw I saw this example: https://rosettacode.org/wiki/Concurrent_computing#Forth 21:29:08 The socket library has a timeout functionality: set-socket-timeout ( u -- ) 21:29:30 oh this is what im looking for :O 21:29:35 sec let me try it 21:30:13 like this right? set-socket-timeout 2ms 21:35:07 the value would go first, so (assuming 2ms is a constant you've defined): 2ms set-socket-timeout 21:36:33 * crc doesn't use gforth, and both of my gforth installs are broken currently, so I can't actually test this myself 21:36:38 hmm it's not showing any error but not working (the timeout) 21:36:53 maybe I need to create a new socket then set the timeout for the new socket 21:37:26 like, a new variable of socket 21:51:49 hmm strange, it's not showing any error on runtime, I put this line before open-socket: 1000 set-socket-timeout but the timeout is not working (even if i put 1 ms) 22:09:44 --- quit: kori (Ping timeout: 252 seconds) 22:25:00 --- quit: ryke (Ping timeout: 245 seconds) 22:41:35 --- join: kori (~kori@arrowheads/kori) joined #forth 22:45:10 --- join: dys (~dys@tmo-102-243.customers.d1-online.com) joined #forth 23:03:22 --- join: farcas82regreg (~regreg@2a02:2f01:8702:7000:ac93:c643:d0f1:8578) joined #forth 23:07:05 --- quit: dys (Ping timeout: 245 seconds) 23:08:03 --- join: dys (~dys@tmo-102-170.customers.d1-online.com) joined #forth 23:11:32 --- quit: Keshl (Read error: Connection reset by peer) 23:12:13 --- join: Keshl (~Purple@207.44.70.214.res-cmts.gld.ptd.net) joined #forth 23:59:59 --- log: ended forth/19.08.19