01:35 <tabemann> ist jemand hier?

01:36 <tp> nein

01:36 <tp> niemand ist hier

01:37 <tabemann> hehe :D

01:37 <tabemann> ugh why do I so not want to implement . ." .( c" or s" ?

01:38 <tp> when you were a young boy a ." scared you badly ?

01:39 <tabemann> nah, it's just that I don't want to figure out how to compile a string into the words being compiled

01:39 <tp> st least it will look like human crafted code when you do it

01:39 <tabemann> maybe it's just that the ADR instruction scares me

01:39 <tp> unlike the stale HAL boilerplate I see as part of embedded C code thesedays

01:40 <tabemann> because it requires a constant to be at a 4-byte offset from the PC

01:40 <tp> the good think about Forth is that it doesnt make the MCU red hot when you screw up

01:40 <tp> just experiment ?

01:40 <tabemann> why doesn't it?

01:40 <tp> it's a benign language

01:41 <tp> all you get is the MCU locking up

01:41 <tabemann> but you can make a tight loop with it if you want to

01:41 <tp> I reset mine a zillion times every project

01:41 <tp> sure, only 3x slower than assembly on average

01:41 <tp> but a tight loop wont hurt the mcu, even when overclocked 6x

01:42 <tp> in the case of a stm32f051

01:43 <tabemann> so why would anything else make the MCU glow?

01:44 <tp> oops I meant 100%

01:45 <tp> well nothing will, modern electronics doesnt do that generally

01:50 <tp> early unix had a 'your printer is on fire' error when it wasnt working, they had to remove it because too many secretaries panicked

01:53 <tabemann> I love that one!

01:53 <tabemann> nah, you can still find that one if you try hard enough

01:55 <tabemann> Modern printer drivers and support have improved and hidden low-level error messages from users, so most Unix/Linux users today have never seen the "on fire" message. However, a few people still run into it today with varying levels of amusement or confusion.[6][7] The "on fire" message remains in the Linux source code as of version 5.0-rc3.[8]

01:55 <tabemann> The message is also present in other software modules, often to humorous effect. For example, in some kernels' CPU code, a CPU thermal failure could result in the message "CPU#0: Possible thermal failure (CPU on fire ?)"[9] and similar humor can be found in the phrase halt and catch fire.

02:05 <tabemann> okay, gotta head home - bbl

02:06 <tp> cya

18:42 <crc> good afternoon