Zarutian_HTC has quit [Read error: Connection reset by peer]
Zarutian_HTC has joined #forth
wineroots has joined #forth
boru` has joined #forth
boru has quit [Disconnected by services]
boru` is now known as boru
dave0 has quit [Quit: dave's not here]
<KipIngram>
Evening gentlemen.
<cmtptr>
MAIN SCREEN TURN ON
sts-q has quit [Ping timeout: 246 seconds]
sts-q has joined #forth
<kiedtl>
I think you meant @MAINSCR TURNON
mtsd has joined #forth
X-Scale` has joined #forth
jyf1 has joined #forth
X-Scale has quit [*.net *.split]
jyf has quit [*.net *.split]
X-Scale` is now known as X-Scale
sts-q has quit [Ping timeout: 240 seconds]
dave0 has joined #forth
sts-q has joined #forth
<dave0>
maw
Zarutian_HTC1 has joined #forth
Zarutian_HTC has quit [Read error: Connection reset by peer]
hosewiejacke2 has joined #forth
hosewiejacke2 has quit [Client Quit]
gravicappa has joined #forth
andrei-n has joined #forth
boru has quit [Read error: Connection reset by peer]
boru has joined #forth
Zarutian_HTC1 has quit [Ping timeout: 240 seconds]
mtsd_ has joined #forth
mtsd has quit [Ping timeout: 240 seconds]
mtsd has joined #forth
mtsd_ has quit [Ping timeout: 252 seconds]
dave0 has quit [Quit: dave's not here]
jedb__ is now known as jedb
Zarutian_HTC has joined #forth
joe9 has quit [Ping timeout: 260 seconds]
joe9 has joined #forth
f-a has joined #forth
f-a has quit [Quit: leaving]
Zarutian_HTC has quit [Ping timeout: 240 seconds]
APic has quit [Ping timeout: 268 seconds]
APic has joined #forth
X-Scale has quit [Ping timeout: 240 seconds]
X-Scale` has joined #forth
X-Scale` is now known as X-Scale
f-a has joined #forth
Zarutian_HTC has joined #forth
f-a has quit [Quit: leaving]
APic has quit [Ping timeout: 268 seconds]
APic has joined #forth
tech_exorcist has joined #forth
APic has quit [Ping timeout: 240 seconds]
APic has joined #forth
Zarutian_HTC has quit [Remote host closed the connection]
f-a has joined #forth
andrei-n has quit [Write error: Connection reset by peer]
andrei-n has joined #forth
f-a_ has joined #forth
f-a has quit [Read error: Connection reset by peer]
f-a_ has quit [Client Quit]
f-a has joined #forth
APic has quit [Ping timeout: 240 seconds]
APic has joined #forth
f-a has quit [Read error: Connection reset by peer]
f-a has joined #forth
Zarutian_HTC has joined #forth
Kumool has quit [Ping timeout: 265 seconds]
tech_exorcist has quit [Remote host closed the connection]
tech_exorcist has joined #forth
tech_exorcist has quit [Remote host closed the connection]
tech_exorcist has joined #forth
Kumool has joined #forth
gravicappa has quit [Ping timeout: 240 seconds]
gravicappa has joined #forth
Zarutian_HTC has quit [Remote host closed the connection]
_0x1d3 has joined #forth
mtsd has quit [Remote host closed the connection]
mtsd has joined #forth
APic has quit [Ping timeout: 265 seconds]
lispmacs[work] has joined #forth
tech_exorcist has quit [Remote host closed the connection]
tech_exorcist_ has joined #forth
Zarutian_HTC has joined #forth
f-a has quit [Ping timeout: 265 seconds]
f-a has joined #forth
gravicappa has quit [Ping timeout: 260 seconds]
andrei-n has quit [Quit: Leaving]
mtsd has quit [Ping timeout: 240 seconds]
Zarutian_HTC has quit [Read error: Connection reset by peer]
Zarutian_HTC has joined #forth
dave0 has joined #forth
<dave0>
maw
<lispmacs[work]>
hi, I was just wondering: it is fairly common, if you need some array space briefly, to just allot and - allot the memory while inside a word?
wineroots has quit [Read error: Connection reset by peer]
f-a has quit [Quit: leaving]
tech_exorcist_ has quit [Quit: tech_exorcist_]
tech_exorcist has joined #forth
<MrMobius>
you cant really do that since the array and word youre defining share the same ditionary
<MrMobius>
unless you mean after youre done defining all words
<dave0>
lispmacs[work]: it sounds sensible but i'm a newbie
<xybre>
Since allot doesn't assign a word, why would the dictionary matter?
<dave0>
it's a really fast way to get some temporary space.. just an add to allocate and a sub to free
<lispmacs[work]>
thinking it through, you would have to be careful in embedded applications, so you weren't doing a lot of writes to flash code space
<lispmacs[work]>
my mind thinking in the context of flashforth
<lispmacs[work]>
it's a little bit confusing to me
<lispmacs[work]>
but according to FF reference sheet, `,' appends `x' to the current data section
<lispmacs[work]>
and the dictionary is stored in flash memory
<lispmacs[work]>
so storing data that way temporarily would burn out your flash memory
<lispmacs[work]>
if you called that word regularly
<lispmacs[work]>
or is the data section outside of the dictionary?
<lispmacs[work]>
need more sleep
<lispmacs[work]>
wait, in flashforth, there are keywords to set which memory type data section is currently referring to - ram, eeprom, or flash
tech_exorcist has quit [Quit: tech_exorcist]
Zarutian_HTC has quit [Read error: Connection reset by peer]