boru` has joined #forth
boru has quit [Disconnected by services]
boru` is now known as boru
<tabemann> tp: I committed the code including FREE as well as the RAM/flash dictionary space validation code
<tp> tabemann, excellent, I couldnt find 'free' when I tested it now I know why!
<tabemann> so now if it's running low on RAM or flash (i.e. < 1K) left it'll complain
dddddd has quit [Ping timeout: 264 seconds]
<tp> perfect, it might become useful soon!
<tabemann> you'll need to rebuild the kernel, for the record
<tp> no problem
<tabemann> also, I got my Numworks calculator in the mail
<tp> whats it like ?
<tp> can you feel the quality ?
<tabemann> the aesthetics and design are nice, but of course entering text is easier said than done
<tabemann> thanks to the college board it can't have a real qwerty keyboard
<tabemann> I'm trying to see if there's any way to lock alpha mode
<tp> unless you make one possible with usb ?
<tabemann> when I port zeptoforth to the board I could add alpha-lock
<tabemann> s/board/calculator
<tp> I have a small fold open bluetooth qwerty keyboard, it's about 10 years old now
<tp> I bought it to use with my old Nokia N70
<tp> it's pretty nice but a Google just failed toi find it, probably discontinued now
<tabemann> you can definitely find bluetooth qwerty keyboards for tablets and like
<tabemann> my dad has one
<tp> yeah, I see lots of them, just not the one I have which is really nice, came in a pouch etc
<tp> the only drawback is ... bluetooth as a usb wireless dongle would have been far better
<tabemann> a lot of products these days have those dongles rather than bluetooth
<tp> yeah, much better
<tp> free unable to parse: free
<tp> what am I doing wrong ?
<tp> tabemann, suggestion: have mcu type and zeptoforth version number in boot up greeting ?
<tp> ahh I know, I recompiled then used a prebuilt binary!
<tp> no thats not it as the prebuilts are rebuilt also with make
<tabemann> the only difference between the prebuilts and the non-prebuilts is that the prebuilts *_full* images are generated through a semi-automated process
<tp> yes
<tp> what is the see command ?
<tabemann> SEE?
<tabemann> SEE
<tabemann> SEE my-word
<tp> oops
<tp> I meant the free command
<tabemann> FREE
<tp> I like your see-for-gas, and I'm close to trying it
<tp> tabemann, ahh, so if I rebuild the kernel then I need to load all the *.fs files after manually or scripted
<tabemann> yeah
<tp> I cant build a zeptoforth_full-0.5.4.bin from make as I dont have the same serial setup as you
<tabemann> actually, you can, because you use utils/build.sh and it requires you to specify a serial port
<tabemann> you don't need e4thcom, but you do need python 3, because the codeload3.py script it uses is written for python 3
<tp> oh, I might try that
<tp> I have a few versions of every python version (yuk)
<tabemann> actually, use build.sh and make_full.sh
<tp> okies
<tabemann> build.sh builds for every supported platform
<tabemann> make_full.sh builds a *_full* binary for a specific platform
<tabemann> note that build.sh requires one to specify a version number
<tabemann> which can be anything not containing a slash
<tabemann> make_full.sh requires a version number, a platform, and a serial port
<tp> cool
<tabemann> note that sometimes make_full.sh hiccups for some reason and won't load the code
<tp> I'll try make_full.sh
<tabemann> you need to do build.sh first
<tp> oh, ok
<tp> no problem, I love automation
<tp> tabemann, two additions would make Zeptoforth a lot friendler imho, 1) mcu type and version number in boot up greeting and 2) a word search facility like Crests "match"
<tabemann> I have LOOKUP
<tabemann> well, LOOKUP looks for prefixes
<tabemann> LOOKUP prefix looks up the words that all share a maximal prefix of "prefix"
<tabemann> so
<tabemann> LOOKUP wo
<tabemann> looks up all the words that start with "wo"
<tp> oh thats cool
<tabemann> and if there are none
<tp> that will do!
<tabemann> all the words that start with "w"
<tabemann> and if there are none
<tabemann> all the words
<tp> excellent
<tabemann> it also does it in four columns
<tp> even better!
<tabemann> bbs - gotta put my daughter to bed
<tp> no problemo
cheater has quit [Ping timeout: 264 seconds]
<tabemann> back
<tabemann> hey, I've got a new version that displays kernel platform, version, and build date
<tabemann> no release yet, but it's in git now
<tp> awesome
<tp> I use git only
iyzsong- has joined #forth
iyzsong has quit [Ping timeout: 272 seconds]
<tabemann> one note about free
<tp> there is a cost ?
<tabemann> what it measures w.r.t. RAM space is the RAM space left in the main task's dictionary
<tabemann> also you have to have multitasking compiled for it to be available
<tp> oh
<tp> well thats ok
<tp> you dont have to use it multitasking tho ?
<tp> just have it compiled ?
<tabemann> well compiling multitasking turns it on
<tabemann> even if there is only one task
<tp> ahh
<tp> still ok
<tabemann> oh and btw you don't need to build it like you're doing a release to set the version
<tabemann> just do:
<tabemann> make PLATFORM=<your platform> VERSION=<your version>
<tp> cool
<tabemann> it automatically gets the current time and date
<tp> nice
<tabemann> if you use utils/build.sh it uses the version you feed it to specify the version for each platform built
<tp> ill try it soon
gravicappa has joined #forth
<tabemann> release 0.5.5 is out!
<tp> awesome!
<tabemann> it'd been a while since I'd done a release, even a patch-level one
<tabemann> I figured I'd accumulated enough changes that it'd be worth it to do a new release, even if none of the individual changes by itself seemed to deserve a release
<tp> cool I'll just dl 5.5.5
_whitelogger has joined #forth
<tabemann> okay, I'm gonna head off to bed now
<tp> nighto!
<tabemann> g'night
WickedShell has quit [Remote host closed the connection]
dys has joined #forth
cheater has joined #forth
kori has joined #forth
kori has joined #forth
kori has quit [Changing host]
xek has joined #forth
xek has quit [Client Quit]
proteusguy has quit [Ping timeout: 256 seconds]
proteus-guy has quit [Ping timeout: 258 seconds]
proteus-guy has joined #forth
proteusguy has joined #forth
reepca has joined #forth
dddddd has joined #forth
_whitelogger has joined #forth
_whitelogger has joined #forth
_whitelogger has joined #forth
cheater has quit [Ping timeout: 265 seconds]
MrMobius has quit [Ping timeout: 246 seconds]
dave0 has quit [Quit: dave's not here]
iyzsong- has quit [Quit: ZNC 1.7.1 - https://znc.in]
X-Scale` has joined #forth
X-Scale has quit [Ping timeout: 264 seconds]
X-Scale has joined #forth
X-Scale` has quit [Ping timeout: 272 seconds]
TCZ has joined #forth
kori has quit [Read error: Connection reset by peer]
kori has joined #forth
kori has quit [Changing host]
kori has joined #forth
TCZ has quit [Quit: Leaving]
antaoiseach has joined #forth
antaoiseach has quit [Quit: leaving]
dys has quit [Ping timeout: 246 seconds]
_whitelogger has joined #forth
reepca has quit [Read error: Connection reset by peer]
reepca has joined #forth
andrei-n has joined #forth
<andrei-n> So, it seems that the C interface cannot include local c files. Is there any solution? Only <> includes work...
<andrei-n> I mean in gforth.
gravicappa has quit [Ping timeout: 246 seconds]
Zarutian_HTC has quit [Ping timeout: 240 seconds]
andrei-n has quit [Quit: Leaving]
Zarutian_HTC has joined #forth
kamid has quit [Quit: WeeChat 2.7.1]
<tabemann> hey guys
<tp> hey tabemann
* tabemann is annoyed that he bought a male breakout board for USB A rather than a female breakout board
<tp> free
<tp> main task dictionary free: 128984
<tp> flash dictionary free: 917500
<tp> main task rstack free: 460 ok
<tp> main task stack free: 504
<tp> bummer
<tabemann> how so
<tp> USB A I mean
<tp> ram-end hex. 20020000 ok
<tp> ram-here hex. 20000410 ok
<tp> $20020000 $20000410 - .decimal 130032 ok
<tabemann> that's because the stacks are at the end of RAM
<tp> Zeptoforth is working fine :)
<tabemann> 130032 1024 - task - . 128984 ok
<tp> is my 130032 above the remaining ram ?
<tabemann> yes
<tp> what is 128984 ?
<tabemann> because the about you get from ram-end ram-here - includes the task record and the stacks for the main task
<tabemann> *because what you get
<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
<tabemann> new tasks' space grow downwards in memory
<tp> I'm not a big task user with embedded, they use too many of the scant resources
<tp> 2 tasks is fine so I can use the terminal during development
<tabemann> that's why I provided a scheduler for sharing a single task amongst multiple scheduled actions
<tp> you have covered all bases!
<tabemann> I'm looking at the eForth FOR ... NEXT functionality, and it is weird
<tabemann> like I don't get why one would even want DO when one can have ?DO
<tabemann> and FOR NEXT behaves the same way except it has a weird AFT word which is used to work around it
<tp> what are you running eforth on ?
<tabemann> I'm not running it
<tabemann> I'm just reading what the STM8EF guy, Thomas, has written about it
<tp> aha
<tp> ?DO doesnt work if 0 so maybe DO is for cases when 0 has to work ?
<tabemann> ?DO checks if the two starting values are equal
<tabemann> and if they are, it jumps out of the loop
<tp> oops oh yeah
<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
<tabemann> but I'm gonna have dinner in a sec, so bbl
karswell_ has joined #forth
karswell_ is now known as karswell
<tabemann> back
dave0 has joined #forth
kamid has joined #forth
rdrop-exit has joined #forth