<rdrop-exit>
b +---+---+---+----+---+---+---+---+---+--+---+---+--+--+--+---+
<rdrop-exit>
c |^? |
<rdrop-exit>
d |7f |
<rdrop-exit>
e |del|
Bunny351 has quit [Remote host closed the connection]
<rdrop-exit>
f +---+
<rdrop-exit>
although xon and xoff aren't official ASCII, they're almost universally assigned to ^Q and ^S
Bunny351 has joined #forth
<tabemann>
back
<rdrop-exit>
In Unix they can be enabled/disabled with the IXOFF IXON terminal mode control flags
<tabemann>
hey rdrop-exit
<rdrop-exit>
hi tabemann
* tabemann
is working on docs
<tabemann>
I've got docs written for all the words one really cares about in the zeptoforth kernel
<rdrop-exit>
the assigned characters can be changed with c_cc[VSTART] and c_cc[VSTOP]
<tabemann>
i.e. not the assembler words, various internal words, or the exceptions
<rdrop-exit>
kudos tabemann
<tabemann>
they're very basic docs though
<tabemann>
just the name of the word and the stack signature
<tabemann>
I'm going to go back and actually add meanings later
<rdrop-exit>
docs are a lot of work
<rdrop-exit>
if you scroll back in the history, I posted about xon/xoff
<tabemann>
I saw
<rdrop-exit>
cool
<rdrop-exit>
lunch is on the table, catch you later, stay healthy
rdrop-exit has quit [Quit: Lost terminal]
gravicappa has joined #forth
<tp>
Zarutian_HTC, welcome back! we were worried you had frozen into the ice in your northern wastelands!
<Zarutian_HTC>
tp: it is more of a slush at this time of year
<tp>
Zarutian_HTC, yes, it's the end of your summer now ?
<Zarutian_HTC>
tp: nope, nearing the start of spring
<tp>
Zarutian_HTC, I surmised that the ice was melting and you had thawed out enough to type ?
<Zarutian_HTC>
tp: well, you see how non-glacial my response are
<tp>
Zarutian_HTC, I do!
<tp>
Zarutian_HTC, how was your winter ? our summer was hell this year
<Zarutian_HTC>
tp: lesse one major storm that affected infrastructure in the northen parts
<Zarutian_HTC>
tp: at least two more that one would not be cought outside in
<tp>
Zarutian_HTC, did you get a chance to do any Forth of late ?
<Zarutian_HTC>
tp: one snow avalance obliterating a harbour and a few small ships in it
<tp>
29,93 C / 85,77 F at my desk right now, 1635 hrs in NSW, australia
<tp>
Zarutian_HTC, thats amazing as I live in a snow and ice free, flat land
<tp>
I believe in a flat Australia but a round world
<Zarutian_HTC>
week before this one an earth quake big enough to be felt in the capital area
<tp>
Zarutian_HTC, perhaps it was just some ice flow breaking ?
<Zarutian_HTC>
tp: nope it was due to earth bedrock resettling due to earlier magma collection under a small part of the Reykjanes penisula
dddddd has quit [Ping timeout: 250 seconds]
<Zarutian_HTC>
this country is geologically after all
<tp>
Zarutian_HTC, you get all the excitement, we just get heat and smoke!
<Zarutian_HTC>
active*
<tp>
Zarutian_HTC, Iceland does sound very interesting
<Zarutian_HTC>
oh yeah a local trumpster not only managed to get drunk and steal a cement truck but most likely he is the arsonist behind a fire of a downtown bar
<Zarutian_HTC>
tp: at least there are no polarbears here like on Svalbard
<tp>
that's the way! we never have anything interesting like that!
<Zarutian_HTC>
some of those bears have been found out to be bi possibly due to pollution
<tp>
Zarutian_HTC, I looked thru Google photos of your area after we last spoke here, it seemed very isolated
<Zarutian_HTC>
tp: what do you mean? i thought australia had lots of murderous fauna
<tp>
Zarutian_HTC, only snakes and spiders really, nothing big but Dingos (like a dog) but they dont attack people
<tp>
the weather is very dangerous because of the lack of water and the heat
<Zarutian_HTC>
tp: depends on where. The capital area is quite relativly nonisolated
<tp>
Zarutian_HTC, Icelanders who have offended Odin have to come to Australia to stay after they die
<Zarutian_HTC>
tp: and escape the wet and cold misery? prepostourus
<tp>
haha
<tp>
how far to Svalbard for you ?
<Zarutian_HTC>
tough honestly I could do without any more ash erruptions
<Zarutian_HTC>
quite the distance really
<tp>
ouch, volcanic ash is bad!
<tp>
we had months of smoke, but that was just burning trees
<Zarutian_HTC>
and there is no direct flight nor ferry between Iceland and Svalbard
<tp>
no silicon to tear up our lungs, just carcinogenic tree smoke
* tabemann
extracted the comments from much of his Forth code to produce docs
<tp>
we had hundreds of fires burning for months, and no water to put them out
<tabemann>
unlike the kernel docs, most of it actually says (basically) what it does
<tp>
tabemann, excellent
<tabemann>
(I omitted the words that I viewed as being internal)
<Zarutian_HTC>
the silica settled out quite quickly after the last erruption ended but man the stuff is nasty on equipment
<tp>
Zarutian_HTC, I prefer tree smoke :)
<tabemann>
why does Australia even have stuff to burn left
<tabemann>
it seems as if Australia is constantly aflame
<Zarutian_HTC>
tp: saw the aftermath of one compressor cooling unit getting clogged with the stuff
<Zarutian_HTC>
tabemann: well there are a few politicans that might work as fuel
<tp>
tabemann, the areas are so vast
<tp>
Zarutian_HTC, yuk, I can believe it
<Zarutian_HTC>
tp: how was it. After two hours drive out of a city you arent in the next one just two hours outside it
<tp>
Zarutian_HTC, i had a lot of problems with silicon dust here for a few years
<tp>
Zarutian_HTC, there was a 'sand blasting' company next door and clouds of fine sand would blow everywhere
<Zarutian_HTC>
tp: the description of the aftermath on thay unit was something on the lines of „anally sandblasted“
<tabemann>
surely you mean silica dust, not silicon dust ;) having problems with silicon dust would be, well, weird
<tp>
tabemann, yes of course, my mistake
<Zarutian_HTC>
tabemann: you know like you get in filesystems on flashdrives
<tp>
Zarutian_HTC, yes silica dust is very hard and sharp
<Zarutian_HTC>
tp: not to mention electro statically nasty
<tabemann>
okay, I'm gonna head off to bed
<tp>
Zarutian_HTC, i didnt know that
<tabemann>
g'night guys
<tp>
night-o tabemann
<tp>
Zarutian_HTC, I'm off for a while myself, thanks for the chat!
<Zarutian_HTC>
tp: at least the ash kind. Fried a board in externally housed UPS for one ofvhe datacenters here
<Zarutian_HTC>
good night
cartwright has quit [Ping timeout: 240 seconds]
Mellowlink has quit [Ping timeout: 240 seconds]
Mellowlink has joined #forth
cartwright has joined #forth
Mellowlink has quit [Ping timeout: 240 seconds]
cartwright has quit [Read error: Connection reset by peer]
cartwright has joined #forth
Mellowlink has joined #forth
iyzsong has quit [Ping timeout: 246 seconds]
iyzsong has joined #forth
xek has joined #forth
actuallybatman has quit [Ping timeout: 250 seconds]
xek has quit [Ping timeout: 250 seconds]
<veltas>
Who is dddddd? They were asking me about some computers before I went on holiday to a place without internet
<veltas>
Oh well catch them later I suppose
_whitelogger has joined #forth
dddddd has joined #forth
iyzsong has quit [Ping timeout: 246 seconds]
dave69 has joined #forth
dave0 has quit [Disconnected by services]
dave69 is now known as dave0
dave0 has quit [Quit: dave's not here]
dddddd_ has joined #forth
deesix has quit [Ping timeout: 264 seconds]
dddddd has quit [Ping timeout: 246 seconds]
dddddd_ is now known as dddddd
deesix has joined #forth
Zarutian_HTC has quit [Quit: Bye]
xek has joined #forth
<veltas>
In the book "Starting FORTH", DEPTH is defined as : DEPTH S0 @ 'S - 2/ 2- ;
<veltas>
That doesn't make any sense to me, does this actually work on any Forth?
<veltas>
I'm confused that S0 would be a variable, and not just return the base of the stack, it's been mentioned elsewhere that S0 is "beyond" the stack so one cell must be removed, but the 2- is done after dividing
<veltas>
So that's like compensating for 2 cells ( i.e. 2/ 2- is the same as 4 - 2/ )
<tabemann>
back
actuallybatman has joined #forth
<tabemann>
that's simple
<tabemann>
it assumes 16 bit cells
<tabemann>
S0 @ must be the bottom of the stack
<tabemann>
there is a mistake though
<tabemann>
2- should be before 2/ or it should be 1- after 2/
jsoft has quit [Ping timeout: 264 seconds]
f-a has joined #forth
<f-a>
so, are you all hoarding... tp?
<f-a>
( ͡° ͜ʖ ͡°)
<veltas>
tabemann: Okay that is my guess, would be very confusing to someone typing that in though, given this is meant to be a helpful example early on
f-a has quit [Quit: leaving]
rdrop-exit has joined #forth
<rdrop-exit>
veltas, I think that's a typo
<rdrop-exit>
in the first edition of Starting Forth (the 79 standard one)
<rdrop-exit>
The 2nd edition (i.e., the 83 standard compliant one) doesn't define DEPTH
actuallybatman has quit [Quit: leaving]
<rdrop-exit>
A more typical defintion of depth on a 16 bit system would be
<rdrop-exit>
sp@ s0 @ swap - 2/
<rdrop-exit>
veltas, to answer your question on why s0 needs to be fetched, it's because s0 is a USER variable on multi-tasking Forths since each task has its own
<rdrop-exit>
gotta sleep, goodnight
rdrop-exit has quit [Quit: Lost terminal]
tabemann has quit [Ping timeout: 250 seconds]
Zarutian_HTC has joined #forth
tabemann has joined #forth
gravicappa has quit [Ping timeout: 264 seconds]
<tabemann>
hey guys
<veltas>
tabemann: hey
* tabemann
just fixed a nasty bug that was causing stack problems, but inexplicably wasn't causing zeptoforth to crash despite also generating corrupt machine code
<tabemann>
I only found the bug because there was another bug that was causing an extraneous value to be put on the stack which I had just fixed
<veltas>
And that caused an actual effect from the nasty bug?
xek has quit [Ping timeout: 240 seconds]
<tabemann>
yes
<tabemann>
the actual bug was that when UNTIL was compiling a 32-bit beq word - which only occurred with a long enough of a jump - it was erroneously not exiting but rather also compiling a 16-bit beq word
<tabemann>
which was taking up a cell from the stack for a destination address
<tabemann>
but even though this instruction would be garbage, it would still be a beq instruction
<tabemann>
and because the status register would already be set for Z == 0, this one wouldn't branch either
actuallybatman has joined #forth
Bunny351 has quit [Remote host closed the connection]
Bunny351 has joined #forth
<veltas>
Nasty
<veltas>
I'm only permitting 8-bit jumps in my forth
<MrMobius>
can you trap bad instructions on ARM?
<veltas>
But they are all directed with logical bases, i.e. the 8-bit 'jump' used for an IF considers the next forth instruction following IF+jump as 0, and goes to 255. Likewise the LOOP jump distance starts at the LOOP itself and goes 255 back.
<veltas>
MrMobius: Apparantly the undefined instruction exception is the same as the divide by 0 exception
<veltas>
So from that I will assume you have a decent amount of control in baremetal and also in a hosted program