00:00:00 --- log: started forth/20.05.30
00:11:31 --- join: cheater joined #forth
00:34:23 --- join: kori joined #forth
00:34:23 --- quit: kori (Changing host)
00:34:23 --- join: kori joined #forth
00:49:02 --- join: xek joined #forth
00:50:23 --- quit: xek (Client Quit)
00:51:21 --- quit: proteusguy (Ping timeout: 256 seconds)
00:51:32 --- quit: proteus-guy (Ping timeout: 258 seconds)
01:04:24 --- join: proteus-guy joined #forth
01:05:06 --- join: proteusguy joined #forth
01:05:06 --- mode: ChanServ set +v proteusguy
01:05:29 --- join: reepca joined #forth
02:58:58 --- join: dddddd joined #forth
03:03:23 --- quit: _whitelogger (Remote host closed the connection)
03:06:26 --- join: _whitelogger joined #forth
03:39:24 --- quit: _whitelogger (Remote host closed the connection)
03:42:27 --- join: _whitelogger joined #forth
05:15:24 --- quit: _whitelogger (Remote host closed the connection)
05:18:27 --- join: _whitelogger joined #forth
05:41:14 --- quit: cheater (Ping timeout: 265 seconds)
05:42:05 --- quit: MrMobius (Ping timeout: 246 seconds)
06:35:54 --- quit: dave0 (Quit: dave's not here)
07:24:13 --- quit: iyzsong- (Quit: ZNC 1.7.1 - https://znc.in)
08:08:04 --- join: X-Scale` joined #forth
08:10:47 --- quit: X-Scale (Ping timeout: 264 seconds)
08:12:06 --- join: X-Scale joined #forth
08:14:08 --- quit: X-Scale` (Ping timeout: 272 seconds)
09:26:49 --- join: TCZ joined #forth
09:30:25 --- quit: kori (Read error: Connection reset by peer)
09:30:55 --- join: kori joined #forth
09:30:55 --- quit: kori (Changing host)
09:30:55 --- join: kori joined #forth
09:38:07 --- quit: TCZ (Quit: Leaving)
10:37:19 --- join: antaoiseach joined #forth
10:52:56 --- quit: antaoiseach (Quit: leaving)
11:55:53 --- quit: dys (Ping timeout: 246 seconds)
12:36:24 --- quit: _whitelogger (Remote host closed the connection)
12:39:27 --- join: _whitelogger joined #forth
13:16:51 --- quit: reepca (Read error: Connection reset by peer)
13:17:08 --- join: reepca joined #forth
13:47:21 --- join: andrei-n joined #forth
14:11:21 <andrei-n> So, it seems that the C interface cannot include local c files.  Is there any solution?  Only <> includes work...
14:11:30 <andrei-n> I mean in gforth.
14:16:56 --- quit: gravicappa (Ping timeout: 246 seconds)
14:37:56 --- quit: Zarutian_HTC (Ping timeout: 240 seconds)
14:43:09 --- quit: andrei-n (Quit: Leaving)
15:04:04 --- join: Zarutian_HTC joined #forth
15:08:53 --- quit: kamid (Quit: WeeChat 2.7.1)
15:12:53 <tabemann> hey guys
15:13:16 <tp> hey tabemann 
15:13:24 * tabemann is annoyed that he bought a male breakout board for USB A rather than a female breakout board
15:13:30 <tp> free 
15:13:30 <tp> flash dictionary free:     917500
15:13:30 <tp> main task dictionary free: 128984
15:13:30 <tp> main task stack free:      504
15:13:30 <tp> main task rstack free:     460 ok
15:13:38 <tp> bummer
15:13:47 <tabemann> how so
15:14:25 <tp> USB A I mean
15:14:40 <tp> ram-end hex. 20020000 ok
15:14:40 <tp> ram-here hex. 20000410 ok
15:14:41 <tp> $20020000 $20000410 - .decimal  130032 ok
15:15:11 <tabemann> that's because the stacks are at the end of RAM
15:15:31 <tp> Zeptoforth is working fine :)
15:18:54 <tabemann> 130032 1024 - task - .  128984 ok
15:20:41 <tp> is my 130032 above the remaining ram ?
15:20:49 <tabemann> yes
15:21:04 <tp> what is 128984 ?
15:21:23 <tabemann> because the about you get from ram-end ram-here - includes the task record and the stacks for the main task
15:21:43 <tabemann> *because what you get
15:22:20 <tabemann> task records are stored high in memory, and the task record for the main task is stored immediately below its data and return stacks
15:22:51 <tabemann> new tasks' space grow downwards in memory
15:23:56 <tp> I'm not a big task user with embedded, they use too many of the scant resources
15:24:21 <tp> 2 tasks is fine so I can use the terminal during development
15:24:39 <tabemann> that's why I provided a scheduler for sharing a single task amongst multiple scheduled actions
15:25:20 <tp> you have covered all bases!
15:37:59 <tabemann> I'm looking at the eForth FOR ... NEXT functionality, and it is weird
15:38:14 <tabemann> like I don't get why one would even want DO when one can have ?DO
15:38:39 <tabemann> and FOR NEXT behaves the same way except it has a weird AFT word which is used to work around it
15:39:57 <tp> what are you running eforth on ?
15:40:35 <tabemann> I'm not running it
15:41:00 <tabemann> I'm just reading what the STM8EF guy, Thomas, has written about it
15:41:14 <tp> aha
15:42:22 <tp> ?DO doesnt work if 0 so maybe DO is for cases when 0 has to work ?
15:44:09 <tabemann> ?DO checks if the two starting values are equal
15:44:59 <tabemann> and if they are, it jumps out of the loop
15:45:12 <tp> oops oh yeah
15:52:32 <tabemann> the thing about ?DO versus DO is that ?DO is obviously the better design, and we are just stuck with DO because of historical precedent
15:53:05 <tabemann> but I'm gonna have dinner in a sec, so bbl
16:11:35 --- join: karswell_ joined #forth
16:22:17 --- nick: karswell_ -> karswell
16:25:02 <tabemann> back
16:31:41 --- join: dave0 joined #forth
16:43:16 --- join: kamid joined #forth
16:50:04 --- join: rdrop-exit joined #forth
17:11:45 <tabemann> hey
17:12:04 * tabemann is busy adapting zeptoforth to run on the numworks calculator
17:12:17 <tabemann> the kernel changes are quite minimal
17:13:02 <rdrop-exit> hey
17:13:34 <tabemann> really the only thing that needed changing in the kernel was the clock/UART init code
17:14:26 <tabemann> the bigger changes will be in the "userland", partly because I renamed some stuff from ANS (b@ rather than c@ e.g.), and also so it behaves well with my multitasking and like
17:15:46 <tp> hey rdrop-exit 
17:16:10 <tp> tabemann, the advantage of writing a Forth for arm
17:16:23 <tp> or more accurately, Cortex-M
17:16:24 <rdrop-exit> hi tp
17:18:19 <tabemann> hey tp
17:19:17 <tp> tabemann, at least it's easy to change command names with Forth :)
17:19:53 <tabemann> he
17:19:55 <tabemann> heh
17:20:00 <tp> I have file that changes names in Zeptoforth to names Im familiar with
17:20:08 <tp> easy peasy
17:23:26 <rdrop-exit> "userland" :)
17:26:01 <tp> thats me, I live in userland
17:26:04 <tabemann> I know it's a fuzzier concept when you don't have protected memory
17:27:31 <rdrop-exit> very Unixy
17:41:32 --- quit: karswell (Remote host closed the connection)
17:41:51 --- join: karswell_ joined #forth
18:11:15 --- join: boru` joined #forth
18:11:18 --- quit: boru (Disconnected by services)
18:11:21 --- nick: boru` -> boru
18:34:27 --- quit: karswell_ (Read error: No route to host)
18:40:51 --- quit: jedb (Ping timeout: 265 seconds)
18:45:24 --- quit: _whitelogger (Remote host closed the connection)
18:48:27 --- join: _whitelogger joined #forth
20:01:08 --- quit: Zarutian_HTC (Ping timeout: 260 seconds)
20:01:58 --- join: Zarutian_HTC joined #forth
20:48:24 --- quit: _whitelogger (Remote host closed the connection)
20:51:27 --- join: _whitelogger joined #forth
20:54:14 --- quit: dddddd (Ping timeout: 256 seconds)
21:21:28 <tabemann> back
22:05:25 --- join: gravicappa joined #forth
22:10:32 <tabemann> tp
22:10:43 <tabemann> about changing names
22:10:51 <tp> yes?
22:10:54 <tabemann> if you want to change b@ to c@
22:11:03 <tp> actually it's not that
22:11:12 <tabemann> you should do it : c@ b@ [inlined] ;
22:11:53 <tp> this is some of my list
22:11:56 <tp> : hex. ( u -- u ) h.8 ;  \ for zeptoforth
22:11:57 <tp> : . .decimal ;
22:11:57 <tp> : compiletoflash compile-to-flash ;
22:11:57 <tp> : compiletoram compile-to-ram ;
22:11:57 <tp> : compiletoram? compiling-to-flash? not ;
22:12:32 <tabemann> . is dependent on base
22:12:54 <tp> there is no standalone "." 
22:13:03 <tp> not in my wordlist
22:13:13 <tabemann> oh wait
22:13:15 <tabemann> I misread that
22:14:07 <tabemann> but for simple words I would suggest adding [inlined] to them
22:14:21 <tabemann> and [inlined] goes before the ;
22:14:23 <tp> I'm just changing names so theyre like Mecrisp-Stellaris which I use all the time
22:14:33 <tp> oh ok
22:14:33 <tabemann> ah
22:18:03 * tabemann should have defined h.8 as : h.8 base @ >r 16 base ! 0 <# # # # # # # # # #> type ;
22:18:08 <tabemann> whoops
22:18:16 * tabemann should have defined h.8 as : h.8 base @ >r 16 base ! 0 <# # # # # # # # # #> type r> base ! ;
22:19:43 <tabemann> I always forget that I now have pictured numeric output
22:19:47 <tp> is there a cornerstone after the full-kernel ?
22:20:08 <tabemann> yes
22:20:10 <tp> so I can delete anything I add
22:20:13 <tp> cool
22:20:14 <tabemann> restore-state
22:21:01 <rdrop-exit> reinstate
22:21:17 <tp> ?
22:21:23 <tp> ah
22:22:09 <rdrop-exit> hi c[] :)
22:22:15 <tabemann> hey rdrop-exit 
22:22:56 <rdrop-exit> hi tabemann
22:23:36 <tabemann> note that anything you really want to go in the binary should go before the restore-state
22:23:58 <tabemann> because at least on F407 that cornerstone wastes a tremendous amount of space
22:24:44 <tabemann> because it has to pad out all the way to the end of the flash sector
22:24:57 <tabemann> due to how flash works on the F407
22:25:14 <tabemann> and the flash sector in question is 64K in size
22:29:32 <tp> tabemann, I havent got that far yet
22:29:56 <tp> tabemann, first I needed the free word to quantify where I was
22:30:28 <tabemann> by the way, if you want to nuke everything but the kernel, there's erase-all
22:30:47 <tp> oh cool
22:31:35 <tabemann> but then you lose all the "full" functionality
22:32:04 <tabemann> it's main use is if you're developing "full" functionality and you make a mistake and need to start over again
22:32:42 <tabemann> *its
22:33:34 <tp> sure
22:33:46 <tp> I do the equivalent a lot on Mecrisp-Stellaris
22:34:17 <tp> ok, I'm nearly ready to try some Forth to gas to add RTS handshaking
23:28:49 --- quit: dave0 (Quit: dave's not here)
23:48:24 --- quit: _whitelogger (Remote host closed the connection)
23:51:27 --- join: _whitelogger joined #forth
23:59:59 --- log: ended forth/20.05.30