<tabemann> hey
* tabemann is busy adapting zeptoforth to run on the numworks calculator
<tabemann> the kernel changes are quite minimal
<rdrop-exit> hey
<tabemann> really the only thing that needed changing in the kernel was the clock/UART init code
<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
<tp> hey rdrop-exit
<tp> tabemann, the advantage of writing a Forth for arm
<tp> or more accurately, Cortex-M
<rdrop-exit> hi tp
<tabemann> hey tp
<tp> tabemann, at least it's easy to change command names with Forth :)
<tabemann> he
<tabemann> heh
<tp> I have file that changes names in Zeptoforth to names Im familiar with
<tp> easy peasy
<rdrop-exit> "userland" :)
<tp> thats me, I live in userland
<tabemann> I know it's a fuzzier concept when you don't have protected memory
<rdrop-exit> very Unixy
karswell has quit [Remote host closed the connection]
karswell_ has joined #forth
boru` has joined #forth
boru has quit [Disconnected by services]
boru` is now known as boru
karswell_ has quit [Read error: No route to host]
jedb has quit [Ping timeout: 265 seconds]
_whitelogger has joined #forth
Zarutian_HTC has quit [Ping timeout: 260 seconds]
Zarutian_HTC has joined #forth
_whitelogger has joined #forth
dddddd has quit [Ping timeout: 256 seconds]
<tabemann> back
gravicappa has joined #forth
<tabemann> tp
<tabemann> about changing names
<tp> yes?
<tabemann> if you want to change b@ to c@
<tp> actually it's not that
<tabemann> you should do it : c@ b@ [inlined] ;
<tp> this is some of my list
<tp> : hex. ( u -- u ) h.8 ; \ for zeptoforth
<tp> : . .decimal ;
<tp> : compiletoram compile-to-ram ;
<tp> : compiletoflash compile-to-flash ;
<tp> : compiletoram? compiling-to-flash? not ;
<tabemann> . is dependent on base
<tp> there is no standalone "."
<tp> not in my wordlist
<tabemann> oh wait
<tabemann> I misread that
<tabemann> but for simple words I would suggest adding [inlined] to them
<tabemann> and [inlined] goes before the ;
<tp> I'm just changing names so theyre like Mecrisp-Stellaris which I use all the time
<tp> oh ok
<tabemann> ah
* tabemann should have defined h.8 as : h.8 base @ >r 16 base ! 0 <# # # # # # # # # #> type ;
<tabemann> whoops
* tabemann should have defined h.8 as : h.8 base @ >r 16 base ! 0 <# # # # # # # # # #> type r> base ! ;
<tabemann> I always forget that I now have pictured numeric output
<tp> is there a cornerstone after the full-kernel ?
<tabemann> yes
<tp> so I can delete anything I add
<tp> cool
<tabemann> restore-state
<rdrop-exit> reinstate
<tp> ?
<tp> ah
<rdrop-exit> hi c[] :)
<tabemann> hey rdrop-exit
<rdrop-exit> hi tabemann
<tabemann> note that anything you really want to go in the binary should go before the restore-state
<tabemann> because at least on F407 that cornerstone wastes a tremendous amount of space
<tabemann> because it has to pad out all the way to the end of the flash sector
<tabemann> due to how flash works on the F407
<tabemann> and the flash sector in question is 64K in size
<tp> tabemann, I havent got that far yet
<tp> tabemann, first I needed the free word to quantify where I was
<tabemann> by the way, if you want to nuke everything but the kernel, there's erase-all
<tp> oh cool
<tabemann> but then you lose all the "full" functionality
<tabemann> it's main use is if you're developing "full" functionality and you make a mistake and need to start over again
<tabemann> *its
<tp> sure
<tp> I do the equivalent a lot on Mecrisp-Stellaris
<tp> ok, I'm nearly ready to try some Forth to gas to add RTS handshaking
dave0 has quit [Quit: dave's not here]
_whitelogger has joined #forth
iyzsong has joined #forth
iyzsong has quit [Ping timeout: 246 seconds]
iyzsong has joined #forth
Zarutian_HTC has quit [Remote host closed the connection]
Zarutian_HTC has joined #forth
_whitelogger has joined #forth
dddddd has joined #forth
_whitelogger has joined #forth
gravicappa has quit [Ping timeout: 265 seconds]
rdrop-exit has quit [Ping timeout: 265 seconds]
rdrop-exit has joined #forth
<neuro_sys> Is forth.org down?
<tp> looks like it is
<neuro_sys> What's a small Forth implementation you are aware for Z80 systems?
rdrop-exit has quit [Ping timeout: 265 seconds]
<siraben> neuro_sys: I've implemented one
<neuro_sys> Thanks!
<siraben> neuro_sys: Here it is not depending on the TI-OS at all, running from boot
rdrop-exit has joined #forth
<siraben> That menu you see was written in Forth.
<neuro_sys> Amazing, I'm checking
<siraben> neuro_sys: In Forth implementation in zkeme80 has a unit test suite written in Forth too, which allowed me to fix some bugs from the ti84-forth repo.
* siraben should implement a Forth REPL for the calculator at some point
<neuro_sys> Doesn't ti84-forth have a REPL already?
<siraben> neuro_sys: Yeah, that works with the TI-OS though.
<neuro_sys> Ah, seems like you compile your Forth code, and then transfer it ti-84
<siraben> Right
<neuro_sys> After I study Forth deeper, I'd like to do the same for Amstrad CPC.
<neuro_sys> There's one Fig-Forth implementation for it from 80s, but it uses 32kb RAM.
<neuro_sys> Hmm, 44K even
<siraben> neuro_sys: Definitely can be smaller. I was very space constrained.
rdrop-exit has quit [Quit: Lost terminal]
gravicappa has joined #forth
iyzsong has quit [Ping timeout: 246 seconds]
iyzsong has joined #forth
<veltas> neuro_sys: I'm working on a Z80 forth for the ZX Spectrum right now, I anticipate the smaller build will be around 8K
<veltas> Forth is a very good fit for 8-bit computers, in my opinion.
cantstanya has quit [Ping timeout: 240 seconds]
cantstanya has joined #forth
iyzsong has quit [Quit: ZNC 1.7.1 - https://znc.in]
<klys> has anyone here heard of in the past an isa or pci card with a microcontroller running forth? I've searched for this and it seems there is no longer evidence for what I remember.
karswell_ has joined #forth
gravicappa has quit [Ping timeout: 258 seconds]
karswell_ has quit [Ping timeout: 246 seconds]
karswell_ has joined #forth
andrei-n has joined #forth
karswell_ is now known as karswell
X-Scale` has joined #forth
X-Scale has quit [Ping timeout: 256 seconds]
X-Scale` is now known as X-Scale
X-Scale` has joined #forth
X-Scale has quit [Ping timeout: 272 seconds]
X-Scale` is now known as X-Scale
WickedShell has joined #forth
WickedShell has quit [Remote host closed the connection]
Zarutian_HTC has quit [Remote host closed the connection]
<neuro_sys> klys: Out of curiosity, what was the card for other than having a microcontroller with forth on it?
<neuro_sys> veltas: Very nice
<neuro_sys> I'm still reading Starting/Thinking Forth slowly, but is there a reference implementation that you guys check?
<neuro_sys> Even though it seems simple enough roll one from just by reading the language spec
gravicappa has joined #forth
karswell has quit [Remote host closed the connection]
karswell has joined #forth
karswell has quit [Remote host closed the connection]
karswell has joined #forth
<veltas> neuro_sys: The reference I see advised before writing a Forth is https://www.bradrodriguez.com/papers/moving1.htm
Zarutian_HTC has joined #forth
<tabemann> hey guys
<klys> neuro_sys, it's not easy to say what other purpose it had, given the date I remember it from, though it is possible it would be used in some future (at the time) bios development.
<tabemann> ah, what every person does when they learn forth - write a forth implementation
* tabemann did the same, and now is on his third forth implementation
<tabemann> (forth has probably the highest implementation to user ratio of any language)
<jackdaniel> look up scheme and generally lisp ,)
gravicappa has quit [Ping timeout: 256 seconds]
reepca has quit [Read error: Connection reset by peer]
reepca has joined #forth
reepca has quit [Read error: Connection reset by peer]
reepca has joined #forth
TCZ has joined #forth
andrei-n has quit [Quit: Leaving]
TCZ is now known as DoomSlayer2020
karswell has quit [Read error: Connection reset by peer]
karswell_ has joined #forth
kamid has quit [Ping timeout: 260 seconds]
lonjil has quit [Ping timeout: 260 seconds]
lonjil2 has joined #forth
lonjil2 is now known as lonjil
DoomSlayer2020 has quit [Quit: Leaving]
tabemann has quit [Read error: Connection reset by peer]
tabemann has joined #forth
<tabemann> hey guys
dave0 has joined #forth
kori has quit [Read error: Connection reset by peer]
<tp> hery tabemann
<tp> tabemann, what does "*** exit status: 0 ***" signify with Zeptoforth ?
<tabemann> tp: nothing
<tp> oh good
<tabemann> that is an error from another program
<tp> oh
<tp> i get it when uploading source to Zeptoforth
<tp> using picocom
<tabemann> that's because it cannot handle zeptoforth rebooting
<tabemann> when loading code zeptoforth frequently reboots
<tabemann> I had to modify codeload3.py so it would tolerate this
<tabemann> (if you're not using e4thcom I'd recommend codeload3.py)
TCZ has joined #forth
<tp> oh ok
<tp> hey I have a code list for you re assembly :)
<tp> tabemann, see http://dpaste.com/3KJRNDK
<tp> thats my initial foray into the gas dissasembly
<tp> next stage is to actually feed it into GAS
WickedShell has joined #forth