remexre has joined #forth
dnm has quit [Ping timeout: 256 seconds]
dnm has joined #forth
heredoc_ has joined #forth
heredoc has quit [*.net *.split]
dave0 has joined #forth
Zarutian_HTC has quit [Remote host closed the connection]
tabemann has quit [Read error: Connection reset by peer]
tabemann has joined #forth
remexre has quit [Quit: WeeChat 2.9]
Zarutian_HTC has joined #forth
boru` has joined #forth
boru has quit [Disconnected by services]
boru` is now known as boru
remexre has joined #forth
jsoft has joined #forth
_whitelogger has joined #forth
_whitelogger has joined #forth
Zarutian_HTC1 has joined #forth
Zarutian_HTC has quit [Read error: Connection reset by peer]
Zarutian_HTC1 has quit [Ping timeout: 272 seconds]
dave0 has quit [Quit: dave's not here]
DKordic has quit []
Zarutian_HTC has joined #forth
gravicappa has joined #forth
_whitelogger has joined #forth
jsoft has quit [Ping timeout: 240 seconds]
pointfree has quit [Read error: Connection reset by peer]
pointfree has joined #forth
X-Scale` has joined #forth
Zarutian_HTC has quit [Ping timeout: 258 seconds]
X-Scale has quit [Ping timeout: 240 seconds]
X-Scale` is now known as X-Scale
jsoft has joined #forth
guan has quit [Read error: Connection reset by peer]
guan has joined #forth
crc has quit [Read error: Connection reset by peer]
crc has joined #forth
gravicappa has quit [Ping timeout: 240 seconds]
boru has quit [Read error: Connection reset by peer]
boru has joined #forth
jsoft has quit [Quit: Leaving]
dave0 has joined #forth
gravicappa has joined #forth
dave0 has quit [Quit: dave's not here]
Zarutian_HTC has joined #forth
Zarutian_HTC has quit [Ping timeout: 240 seconds]
Zarutian_HTC has joined #forth
john_cephalopoda has joined #forth
<john_cephalopoda> Hi
f-a has joined #forth
irsol has quit [Ping timeout: 240 seconds]
mark4 has joined #forth
f-a has quit [Ping timeout: 260 seconds]
f-a has joined #forth
f-a has quit [Client Quit]
Zarutian_HTC has quit [Remote host closed the connection]
proteus-person has quit [Ping timeout: 240 seconds]
proteus-guy has quit [Ping timeout: 260 seconds]
proteus-guy has joined #forth
proteus-person has joined #forth
tabemann has quit [Remote host closed the connection]
tabemann has joined #forth
irsol has joined #forth
Zarutian_HTC has joined #forth
tabemann has quit [Ping timeout: 260 seconds]
gravicappa has quit [Ping timeout: 272 seconds]
gravicappa has joined #forth
Zarutian_HTC has quit [Ping timeout: 272 seconds]
tabemann has joined #forth
f-a has joined #forth
Zarutian_HTC has joined #forth
gravicappa has quit [Ping timeout: 240 seconds]
Zarutian_HTC has quit [Remote host closed the connection]
f-a has quit [Quit: leaving]
_whitelogger has joined #forth
xek has joined #forth
cheater has joined #forth
<cheater> hi forths
<cheater> i was wondering if anyone had thoughts on this: https://www.reddit.com/r/c64/comments/j0y1rv/is_forth_a_good_match_for_6502/
<cheater> "Is Forth a good match for 6502?"
<cheater> basically it's about the fairly underpowered cpu in the C64/C128
<cheater> and whether forth is a good fit for it, performance-wise
<cheater> and if there are any hacks that are required to make it run real good
* cheater looks at the topic
<cheater> why does forth need two stacks? i thought one was enough.
<remexre> one for return addrs, one for data?
xek has quit [Ping timeout: 240 seconds]
_whitelogger has joined #forth
<crc> yes, keeping data and addresses separate
<crc> mixing both complices things as you have to work around the return addresses, and maybe other things (locals, if you have them, loop indices, and such)
<crc> *complicates
TCZ has joined #forth
<mark4> cheater, tom zimmer wrote a forth for the vic20 and the c64 (both cartridge based)
<mark4> forth works good on almost any processor
<mark4> except the low end PICs :)
<tabemann> hey guys
TCZ has left #forth ["Leaving"]
<tabemann> cheater: I imagine the zero page would be well suited for many of the things traditionally kept in registers, including the data stack pointer
dave0 has joined #forth