[2021-03-19 00:52:57] → gravicappa joined (~gravicapp@h109-187-17-216.dyn.bashtel.ru) [2021-03-19 03:36:29] → f-a joined (~f-a@151.36.86.122) [2021-03-19 03:49:14] remexre, that inkplate-6 looks cool. Are there not already esp32 forths around? I haven't looked yet. [2021-03-19 03:50:03] proteusguy: I saw one project announcement, but didn't see a GitHub nor a mailing list, and didn't dig deeper [2021-03-19 03:50:13] (deeper includes looking beyond the first search result) [2021-03-19 04:06:14] What kind of cpu architecture/ISA is esp32? MIPs-like? ARM-like? [2021-03-19 04:22:31] Hmmm... I'm at a loss to find a good description of the ISA and it sounds like access to all the peripherals (like bluetooth) are proprietary C libs. Seems like a chip that I'd want to avoid at all costs. Maybe my google-fu is just no good today? [2021-03-19 04:31:05] is there a way while I'm in a running gforth application to just start a shell? Like, a word/words to temporarily kick back out to the shell that would start when you just run "gforth"? Would be useful for debugging my game because then I can just press some key and mess with stuff without having to write a debug menu [2021-03-19 04:31:19] proteusguy: seen https://raw.githubusercontent.com/eerimoq/hardware-reference/master/esp32/xtensa%20Instruction%20Set%20Architecture%20(ISA)%20Reference%20Manual.pdf ? [2021-03-19 04:31:46] at least their TRM is available to the public: https://www.espressif.com/sites/default/files/documentation/esp32_technical_reference_manual_en.pdf [2021-03-19 04:35:15] nihilazo: tried S" $SHELL" SYSTEM ? [2021-03-19 04:38:59] ah, yeah, that's the system shell, I mean the forth shell (maybe I don't know the proper term for that. like the REPL) [2021-03-19 04:41:42] QUIT? [2021-03-19 04:42:24] (without the ?) [2021-03-19 04:44:23] ah, that works, thanks [2021-03-19 04:44:39] inode, thanks... that's pretty dense stuff but likely what I need. [2021-03-19 04:53:51] ⇐ f-a quit (~f-a@151.36.86.122): Ping timeout: 256 seconds [2021-03-19 04:55:29] → f-a joined (~f-a@151.38.123.175) [2021-03-19 04:58:30] oh it's not as bad as I thought. [2021-03-19 05:05:14] So it's pretty much a RISCy style ISA from what I can tell. Shouldn't be difficult to get a forth going. Would just naturally be a big one I guess it being a 32bit processor and native word size. [2021-03-19 05:09:37] ⇐ f-a quit (~f-a@151.38.123.175): Quit: leaving [2021-03-19 05:42:03] ⇐ jedb quit (~jedb@185.204.1.181): Read error: Connection reset by peer [2021-03-19 05:49:49] → jedb joined (~jedb@185.204.1.181) [2021-03-19 06:25:54] mark4: The OS can probably mask repeats even from a PS/2 keyboard by tracking which keys are currently up/down and ignoring down presses without an up. [2021-03-19 06:26:09] It's turtles all the way down [2021-03-19 06:54:58] → hosewiejacke joined (~hosewieja@i5C742F7A.versanet.de) [2021-03-19 07:39:44] ⇐ hosewiejacke quit (~hosewieja@i5C742F7A.versanet.de): Ping timeout: 240 seconds [2021-03-19 08:13:23] → hosewiejacke joined (~hosewieja@i5C742F7A.versanet.de) [2021-03-19 08:22:38] → tech_exorcist joined (txrcst@gateway/shell/hashbang/x-ibpmdcpyfyflvlfu) [2021-03-19 08:24:35] ⇐ rprimus quit (~micro@unaffiliated/micro): Quit: leaving [2021-03-19 08:24:54] → rprimus joined (~micro@unaffiliated/micro) [2021-03-19 08:55:20] ⇐ jedb quit (~jedb@185.204.1.181): Ping timeout: 240 seconds [2021-03-19 09:00:17] → jedb joined (~jedb@210.1.209.100) [2021-03-19 09:04:32] ⇐ jedb quit (~jedb@210.1.209.100): Ping timeout: 240 seconds [2021-03-19 09:15:16] :) [2021-03-19 09:16:07] OK so how do I debug a forth program lol [2021-03-19 09:16:21] inode i am writing an ESP32 assembler! [2021-03-19 09:16:29] is there any easier way than using gforth's debugging words, which are all basically just slightly fancier print statements lol [2021-03-19 09:16:41] at least as far as I've read the docs [2021-03-19 09:16:41] its almost complete i just have not done that last little bit with it, branch resolution :) [2021-03-19 09:17:24] i have two ESP32 boards here with LORA radios on them that i would love to bring up with forth [2021-03-19 09:28:25] nihilazo, well you cant set variable watches without variables :) [2021-03-19 09:28:38] i usually halt and examine thr stack [2021-03-19 09:29:02] something is filling the float stack with stuff but idk what [2021-03-19 09:29:13] I think I know roughly where it's happening? [2021-03-19 09:29:44] ⇐ hosewiejacke quit (~hosewieja@i5C742F7A.versanet.de): Ping timeout: 240 seconds [2021-03-19 09:29:45] except I don't [2021-03-19 09:30:34] if I have something I've defined with "create devices 0e ,f -1 ," that has two cells, one that contains a floating point number and one that contains a fixed point number [2021-03-19 09:31:02] I think there's something odd in the way I'm handling tracking changes of stuff, I would post code but there's nothing more specific I can do than just post everything and say "it's in here somewhere" [2021-03-19 09:32:27] → dave69 joined (~davezero@069.d.003.ncl.iprimus.net.au) [2021-03-19 09:33:54] ⇐ dave0 quit (~davezero@069.d.003.ncl.iprimus.net.au): *.net *.split [2021-03-19 09:36:30] ⇐ sts-q quit (~sts-q@212.53.219.143): Ping timeout: 246 seconds [2021-03-19 09:49:16] → hosewiejacke joined (~hosewieja@i5C742F7A.versanet.de) [2021-03-19 09:49:25] → sts-q joined (~sts-q@212.53.219.143) [2021-03-19 10:28:23] mark4: nice, are you going to share the sources? [2021-03-19 10:28:38] to my esp32 assembler? [2021-03-19 10:28:39] ⇐ dave69 quit (~davezero@069.d.003.ncl.iprimus.net.au): Quit: dave's not here [2021-03-19 10:28:41] yes [2021-03-19 10:28:43] yea that will be published :) [2021-03-19 10:28:53] really i shud put it on github already lol [2021-03-19 10:29:54] nihilazo: tried DBG under gforth-itc? [2021-03-19 10:30:13] that's what I'm trying now but that's not tracing the float stack which is annoying [2021-03-19 10:30:14] err actually i cant find those sources lol if i lost them it would be a PITA lol [2021-03-19 10:30:22] but sometimes a redo is better than the first time :) [2021-03-19 10:30:34] idk if I can get dbg to show me the float stack too [2021-03-19 10:30:55] (I'm doing a lot of float stuff, which is probably forth heresy, but it's the most reasonable way) [2021-03-19 10:31:04] you can, but you'll need to make your own copy of the offending words from debug.fs [2021-03-19 10:31:21] (or modify it in your site-forth if you don't care about keeping it entact) [2021-03-19 10:31:38] ok [2021-03-19 10:32:12] in (_debug) you'll see a call to d.s, if you stick f.s, next to it you'll get the float stack printed as well [2021-03-19 10:33:37] like s/BEGIN d.s/BEGIN d.s f.s/ [2021-03-19 10:34:15] thanks [2021-03-19 10:37:51] ok phew found my esp32 assembler sources lol [2021-03-19 10:40:02] inode if you would like to see these not yet finished sources i can try dcc them :) [2021-03-19 10:41:13] they are still 99.999999% not even tested yet lol [2021-03-19 10:41:54] i'm not even sure i have dcc support in this irc client :) [2021-03-19 10:42:15] lets try lol [2021-03-19 10:42:43] see it? [2021-03-19 10:42:57] dcc has never really been that reliable [2021-03-19 10:43:08] i could paste the entire sources in here }:) [2021-03-19 10:43:08] well i see a message about connecting to an illogical socket: 0.0.0.199:0 [2021-03-19 10:43:09] lol [2021-03-19 10:43:27] no rush though, i'd have to find the esp32 i got in a pile of parts someone was parting with first [2021-03-19 10:44:10] ya and branch resolution is not done yet, i was working on it but at the time i was doing this i was kind of forcing myself to code [2021-03-19 10:44:28] 99% of my time was dedicated to important things like Ark Survival Evolved! lol [2021-03-19 10:44:31] did you write it in forth? [2021-03-19 10:44:35] yes [2021-03-19 10:47:03] https://dpaste.com/C9J34JQ4F <-- thats my register definitions for it [2021-03-19 10:47:13] cool, are you expecting the usual syntax you'd see xtensa code in or something RPNish? [2021-03-19 10:47:27] oh of course the assembler is written in forth :D [2021-03-19 10:47:43] i dont do RPN assemblers, they totally mess my brain up lol [2021-03-19 10:48:27] https://dpaste.com/4EDGET6TQ <-- the word asm> in this file is now i do assembler in a sane manner :) [2021-03-19 10:49:06] every nemonic starts with asm> which pulls its return address off the stack and replaces it with the return address of the previous nemonic [2021-03-19 10:49:20] xxx reg, reg [2021-03-19 10:49:23] yyy reg [2021-03-19 10:49:40] when yyy is referenceed the reg, reg on the xxx nemonic line will already have been parsed [2021-03-19 10:49:50] we return INTO xxx and complete that opcode [2021-03-19 10:49:56] forth black magic [2021-03-19 10:50:25] when yyy is parsed and executed i mean [2021-03-19 10:51:25] Yeah I don't know how people do RPN assemblers [2021-03-19 10:51:34] fair enough re: brain mess, i'm playing with the idea of generating asm though inline-forth-as-a-preprocessor and relying on `operand [... operandN] mnemonic` syntax at the moment [2021-03-19 10:51:41] Assembly is hard enough already I don't want a hard-mode [2021-03-19 10:52:37] veltas: asm is trival to code once you know all the opcodes, it just requires you do everything yourself so no mommy compiler or library holding your hand :) [2021-03-19 10:52:46] but 5 # ax mov is just horrible [2021-03-19 10:53:04] mov ax, 5 [2021-03-19 10:53:06] push bx [2021-03-19 10:53:10] is readable [2021-03-19 10:53:13] I know Z80 like the back of my hand, but assembly is a lot of juggling register state etc and RPN just makes that even harder [2021-03-19 10:53:41] There's only so much room in my head to write good assembly with, I don't want to use up brainpower trying to learn to write it all backwards too [2021-03-19 10:54:08] lol i have had forth jobs where i was fixing bugs in bass ackwards asm code [2021-03-19 10:54:29] i would literally have to rewrite it all out forwards, fix the bug then write it all bass ackwards for them again [2021-03-19 10:54:30] And to be fair 8-bit assembly is harder than modern assembly, which I write alongside C professionally [2021-03-19 10:55:13] well doing 16/32/64 bit operations on an 8 bit CPU is difficult, most forths for 8 bit computers are 16 bits [2021-03-19 10:55:23] but use forth extensions to give you the 32 bit stuff [2021-03-19 10:55:28] double number extensions etc [2021-03-19 10:55:31] Yeah weird shit in code throws me off and I have to 'clean' it up too as a way of understanding it [2021-03-19 10:55:58] Your code is clean in my books mark4 [2021-03-19 10:57:58] its actually my #1 prime directive to keep it clean... i dont always manage that [2021-03-19 10:58:16] its a sequence of successive approximations lol [2021-03-19 10:58:24] Your code is clean but your interface stinks :P [2021-03-19 10:58:38] like my memory manager in x4/x64 is really bad code that needs to be rewritten [2021-03-19 10:58:53] It should be like the cathedral that SwiftForth is, silent but deadly [2021-03-19 10:58:57] there are things about the interface that are broken right now, it really did not stink this bad originally [2021-03-19 10:59:14] it suffering from slight bitrot atm [2021-03-19 10:59:36] has been bugging me for a cpl of years but my coding get up and go kind of got up and went lol [2021-03-19 11:00:35] I think the key is really it should just be a simple repl like anything else, not this full-terminal thing [2021-03-19 11:00:55] I liked the gforth status bar when they added it at first but I've even gone off of that, just keep it simple [2021-03-19 11:01:00] the full terminal thing is optional [2021-03-19 11:01:13] How do you turn it off [2021-03-19 11:01:21] how do you turn what off [2021-03-19 11:01:31] The full terminal stuff [2021-03-19 11:01:44] cp src/x4.f to src/x4v.f and edit out all the terminfo related sources [2021-03-19 11:01:54] and remove hello and status.f from the build too [2021-03-19 11:02:07] then change ./extend to reference x4v.f [2021-03-19 11:02:15] or you can just say statoff [2021-03-19 11:02:19] turns off the status bar [2021-03-19 11:02:35] you can add that to your ~/.x4.rcf file [2021-03-19 11:02:43] So it's optional in the sense you can patch it out :P [2021-03-19 11:02:56] It should be a switch somewhere or gone IMO [2021-03-19 11:02:59] the commented out smkx in there turns on cursor key handling [2021-03-19 11:03:04] Anyway just my opinion [2021-03-19 11:03:33] veltas lets say you write this application in forth. you develop it with the full extended forth kernel will ALL the bells and whistles that makes development easier [2021-03-19 11:03:50] but you want to create a slimmed down turnkey executable [2021-03-19 11:03:56] Respect otherwise though, if I had to use x4 I could patch it and make it suit me, I couldn't do that for gforth at all as easily despite being interactively closer to what I want [2021-03-19 11:04:20] well you can copy x4.f to somewhere, create a very very slimmed down extended forth compiler and compile your sources on top of that [2021-03-19 11:04:27] then you do ' app-main is default [2021-03-19 11:04:31] turnkey my-app [2021-03-19 11:04:55] now you have ./myapp executable with NO HEADERS and all the bloat thats in ./x4 stripped out [2021-03-19 11:05:22] Nice [2021-03-19 11:05:37] you could just edit src/x4.f and comment out everything you dont want (start at the bottom and work your way up commenting out things you dont want) [2021-03-19 11:06:21] comment out hello.f and utils.f and status.f and re-extend and see that it still works [2021-03-19 11:07:06] then comment out everythig thats inside src/ext/terminal and rebuild - if any of the extensions lower down rely on those you can comment them out too [2021-03-19 11:07:36] ./extend will puke if an extension that relies on the terminal stuff is still in there so you can find deps that way [2021-03-19 11:07:57] Yeah that is what I'd expect [2021-03-19 11:08:21] but i find having the status bar is a great help during devel [2021-03-19 11:08:31] How so? [2021-03-19 11:09:14] i can see how much list space (code space) and how much header space and how many items are on the stack without having to ask [2021-03-19 11:09:25] also, i see what the current radix is [2021-03-19 11:09:36] that number is always expressed in decimal [2021-03-19 11:09:50] so hex is shown as base 16 in the status bar [2021-03-19 11:10:12] the date code is juts eye candy lol [2021-03-19 11:10:14] and broken lol [2021-03-19 11:10:23] cuz they changed the format of the timezone files [2021-03-19 11:17:08] is Jan Engelhardt someone thats in here? [2021-03-19 11:17:41] he cloned my uCurses repo a few days ago and im kind of surprised anyone has found it at all lolk [2021-03-19 11:19:58] ⇐ lispmacs quit (~user@fsf/member/lispmacs): Remote host closed the connection [2021-03-19 11:20:38] I cloned x64 to do some changes and then immediately diverted to other things, it's rare I follow through and actually contribute *on github* [2021-03-19 11:20:53] I do contribute but often just send patches to people directly [2021-03-19 11:36:33] ⇐ shmorgle quit (~patrick@gw.neurotica.com): Ping timeout: 264 seconds [2021-03-19 11:45:59] ya lol [2021-03-19 12:07:13] mark4, are you gonna be able to talk to all these devices at a lower level than C libs for the ESP32 stuff? Definitely interested in your assembler and (presumably) forth targeted there. [2021-03-19 12:08:06] i would like to beb able to take all those low level drivers in c and stuff them all in /dev/null lol [2021-03-19 12:08:22] writing a spi/i2c/uart driver in forth/asm is trivial [2021-03-19 12:08:41] doing low level asm/forth drivers for the rest would also be doable [2021-03-19 12:09:05] i wont be putting any FFIs in there to call C stuff [2021-03-19 12:13:28] → f-a joined (~f-a@151.38.142.44) [2021-03-19 12:24:59] → shmorgle joined (~patrick@gw.neurotica.com) [2021-03-19 12:32:00] ⇐ f-a quit (~f-a@151.38.142.44): Quit: leaving [2021-03-19 12:32:20] → f-a joined (~f-a@151.38.142.44) [2021-03-19 12:52:22] is there an equivalent of f. that will leave off the trailing . if there are no decimal places? [2021-03-19 12:56:06] → [1]MrMobius joined (~MrMobius@208.58.206.154) [2021-03-19 12:56:07] ⇐ MrMobius quit (~MrMobius@208.58.206.154): Ping timeout: 265 seconds [2021-03-19 12:56:27] * [1]MrMobius → MrMobius [2021-03-19 12:56:59] or would I have to write it [2021-03-19 12:58:37] also lmao gforth's implementation of ftrunc is wonderful [2021-03-19 12:58:40] f>d d>f [2021-03-19 13:10:06] ⇐ f-a quit (~f-a@151.38.142.44): Quit: leaving [2021-03-19 13:17:20] ⇐ hosewiejacke quit (~hosewieja@i5C742F7A.versanet.de): Ping timeout: 240 seconds [2021-03-19 13:52:52] mark4: the uCurses repo is missing the `configure` script that `build.sh` tries to run [2021-03-19 14:02:46] → lispmacs[work] joined (~user@fsf/member/lispmacs) [2021-03-19 14:03:22] to get the configure script you have to do autoreconf -fiv [2021-03-19 14:03:29] then cd build and ../configure and then make [2021-03-19 14:03:38] that keeps all the .o files etc OUT of the src dir [2021-03-19 14:03:49] thats the only way you can do that with autotools it pisses me off [2021-03-19 14:04:00] there should be a OUTDIR or somethng [2021-03-19 14:04:20] OBJDIR or it should build all the obj's into /tmp or something [2021-03-19 14:04:25] poluting src is utter bs [2021-03-19 14:05:06] i was going to add all that autoreconf stuff to ./build but i am actually never using ./build now [2021-03-19 14:05:17] i just cd build and run make in there [2021-03-19 14:06:16] also, please ignore all the stuff in main.c thats not really an example of how things are going to be, im working on the key input stuff atm [2021-03-19 14:06:31] and getting frustrated with the utter inadaquicies of terminfo for input [2021-03-19 14:11:05] `cc src/*.c -I./` works to build the example (with some warnings); I had to disable the call to clock_nanosleep() to build it on openbsd [2021-03-19 14:11:32] warnings are errors [2021-03-19 14:11:44] what warnings did you get and what compiler did you build it with? [2021-03-19 14:12:00] i find clang has a much better optimizer than gcc usually [2021-03-19 14:12:47] that whole main.c demo/example code is really just so i can see things working as expected [2021-03-19 14:13:00] you would not have that kind of stuff happening in an actual app using this lib :) [2021-03-19 14:13:11] http://forth.works/share/f830b2533a298c003033b77e8d6b4542 [2021-03-19 14:13:40] wow i dont get those [2021-03-19 14:13:50] thats in format.c [2021-03-19 14:14:02] → [1]MrMobius joined (~MrMobius@208.58.206.154) [2021-03-19 14:14:09] part of the %{ processing if i remember correctly [2021-03-19 14:14:40] parse.c not format.c [2021-03-19 14:15:12] oh ya sorry lol. [2021-03-19 14:15:12] → f-a joined (~f-a@151.38.142.44) [2021-03-19 14:15:31] format.f is what i called it in forth [2021-03-19 14:15:38] its the terminfo format string parser [2021-03-19 14:15:42] so.. parse.c works too :) [2021-03-19 14:15:56] does the code RUN in what ever terminal you are using? [2021-03-19 14:16:09] ⇐ MrMobius quit (~MrMobius@208.58.206.154): Ping timeout: 264 seconds [2021-03-19 14:16:10] * [1]MrMobius → MrMobius [2021-03-19 14:16:12] it does not look right in the linux terminal because many of the utf8 chars are not available there [2021-03-19 14:16:28] it also does not work great in rxvt's or some other terminals [2021-03-19 14:16:33] it does run (under putty on a Windows 10 machine connected to my openbsd box) [2021-03-19 14:16:46] works great in gnome-terminal and konsole [2021-03-19 14:17:20] are there any artifacts in that console when its doing its updates? [2021-03-19 14:17:28] not that I can see [2021-03-19 14:17:34] ok cool [2021-03-19 14:17:41] putty doesnt suck as bad as i thought :) [2021-03-19 14:18:04] nobody in their right mind would do that rainbow effect either lol [2021-03-19 14:18:07] not like that any way [2021-03-19 14:18:30] just testing the full 24 bit rgb display and the gray scale display there [2021-03-19 14:19:25] can you do a make scan? [2021-03-19 14:19:36] that does the clang scan-build make [2021-03-19 14:19:55] and ive been trying to figure out why the scan-build of color.c takes 20+ seconds when every other file takes 1 or 2 max [2021-03-19 14:20:02] I have no makefile [2021-03-19 14:20:18] no autoconf/autotools on this system [2021-03-19 14:20:21] run autoreconf -fiv [2021-03-19 14:20:25] then cd build [2021-03-19 14:20:28] then ../configure [2021-03-19 14:20:29] then make [2021-03-19 14:21:16] how come no autotools? [2021-03-19 14:21:18] ! [2021-03-19 14:21:42] BSD system, I've not needed it for anything thus far :) [2021-03-19 14:21:48] heh [2021-03-19 14:21:56] thats herecy to some people :) [2021-03-19 14:21:58] — crc tries to avoid using the gnu bloatware [2021-03-19 14:22:38] setting it up now, will advise back shortly [2021-03-19 14:22:46] cool [2021-03-19 14:22:53] it can always be purged later :) [2021-03-19 14:22:56] i do that a lot [2021-03-19 14:22:59] emerge blah [2021-03-19 14:23:05] blah foo bar bam [2021-03-19 14:23:09] emerge -c blah [2021-03-19 14:24:19] only 42k stripped. used to be less than that when i was building without autotools [2021-03-19 14:24:26] like 8k less lol [2021-03-19 14:25:06] btw, space pauses the app and enter quits [2021-03-19 14:25:14] i shud really specify that somewhere lol [2021-03-19 14:26:25] ./build.sh[3]: ../confiure: not found [2021-03-19 14:28:07] from outside the ./build dir you need to run autoregen -fiv [2021-03-19 14:28:13] that creates the ./configure [2021-03-19 14:28:22] which you run from inside the build dir and that creates the makefile [2021-03-19 14:28:30] dont use ./build heh [2021-03-19 14:28:35] its kind of incomplete [2021-03-19 14:29:03] cd uCureses && autoreconf -fiv && cd build && make [2021-03-19 14:29:27] erm no after cd build you do ../configure [2021-03-19 14:30:07] mkdir build [2021-03-19 14:30:07] autoreconf -fiv [2021-03-19 14:30:07] cd build [2021-03-19 14:30:07] ../confiure [2021-03-19 14:30:07] make [2021-03-19 14:30:21] would be a working ./build.sh [2021-03-19 14:30:35] after this, I needed to edit the Makefile to change -std=gnu17 to -std=c99 and now the build fails on the warnings in parse.c [2021-03-19 14:30:59] change them to use %lu [2021-03-19 14:31:04] n2 = snprintf(s, 3, "%lu", n1); [2021-03-19 14:31:07] that worked for me [2021-03-19 14:31:15] but i never got those warnings you were getting before [2021-03-19 14:31:55] i think -wall -werror should be universally enforced 100% of the time and not bypassable :) [2021-03-19 14:32:24] %llu worked for me, but the demo built this way is completely broken [2021-03-19 14:32:39] yea llu is not right [2021-03-19 14:33:06] i use llu and it gives me warnings [2021-03-19 14:33:17] with lu I get: [2021-03-19 14:33:19] ../src/parse.c:562: warning: format '%lu' expects type 'long unsigned int', but argument 4 has type 'uint64_t' [2021-03-19 14:33:21] error: format ‘%llu’ expects argument of type ‘long long unsigned int’, but argument 4 has type ‘uint64_t’ {aka ‘long unsigned int’} [-Werror=format=] [2021-03-19 14:33:42] your uint64_t def is not the same as the linux one! [2021-03-19 14:34:01] uint64_t in linux IS a long unsigned int [2021-03-19 14:34:30] cast the uint64_t's to (long unsigned int) for the printf [2021-03-19 14:34:32] ugly lol [2021-03-19 14:35:03] n2 = snprintf(s, 3, "%lu", (long unsigned int) n1); [2021-03-19 14:35:12] etc etc [2021-03-19 14:36:29] i think that your bsd has a broken definition for uint64_t [2021-03-19 14:37:15] uint64_t is an 'unsigned long long' [2021-03-19 14:37:40] not in linux [2021-03-19 14:37:48] in linux ists an unsigned long int [2021-03-19 14:37:55] oh! [2021-03-19 14:38:00] are you on a 32 bit system? [2021-03-19 14:38:41] that might be the problem :) [2021-03-19 14:39:02] the problem is a uint64_t is a unsigned long int on a 64 bit system and an unsigned long long on a 32 bit system :) [2021-03-19 14:40:41] maybe i mean [2021-03-19 14:41:10] no, 64-bit [2021-03-19 14:41:34] ok then someone is defining uint64_t wrong [2021-03-19 14:41:47] they should not be defined differently and obviously they are [2021-03-19 14:42:34] can you cast them to unsigned long ints as above? [2021-03-19 14:46:43] the wikipedia entry https://en.wikipedia.org/wiki/C_data_types lists `long long` for 64-bit, which matches what I've generally seen in my work with C [2021-03-19 14:48:08] ⇐ gravicappa quit (~gravicapp@h109-187-17-216.dyn.bashtel.ru): Ping timeout: 240 seconds [2021-03-19 14:48:13] your casting there fixes the build, but the demo still fails to work correctly :( [2021-03-19 14:48:32] whats it doing? [2021-03-19 14:48:52] → gravicappa joined (~gravicapp@h37-122-125-6.dyn.bashtel.ru) [2021-03-19 14:50:17] instead of doing the cast change the declaration of n1 to unsigned long int? [2021-03-19 14:50:36] and leave then as %ld [2021-03-19 14:52:57] also, replace that ENTIRE switch statement with this one liner lol [2021-03-19 14:52:59] n2 = snprintf(s, digits + 3, "%ld", n1); [2021-03-19 14:54:10] and that just leaves ONE switch statement (well with nested switch statemetns actually) to purge with extreme prejudice from these sources :) [2021-03-19 14:57:50] num_esc += snprintf(&esc_buff[num_esc], digits + 3, "%ld", n1); moar optimizashunz plzkthxbai [2021-03-19 14:58:48] https://dpaste.com/6XSWC6X5F [2021-03-19 14:59:27] → hosewiejacke joined (~hosewieja@i5C742F7A.versanet.de) [2021-03-19 15:00:17] though really im not a fan of snprintf either, i should code this trivial thing by hand [2021-03-19 15:02:15] num_esc += snprintf(&esc_buff[num_esc], digits + 3, "%ld", (unsigned long)fs_pop()); /* get rid of the variable */ [2021-03-19 15:02:46] no that i prefer not to do, statements like that are actually harder to read [2021-03-19 15:03:01] and also harder to optimize sometimes too [2021-03-19 15:03:13] i dont like to bury function calls inside function calls lol [2021-03-19 15:03:20] tho.. i have been known to when being lazy [2021-03-19 15:05:06] I prefer not using variables in most cases [2021-03-19 15:05:22] the optimizer will put that in a reg usually [2021-03-19 15:05:52] fs_push(utf8_strlen(s)); <-- lol me being lazy [2021-03-19 15:06:25] — crc dislikes the optimizer... it breaks my mental model of my code as it relates to the generated assembly [2021-03-19 15:06:50] also, having the variable there makes the code more descriptive too if you give the variable a good name which i rarely do :) [2021-03-19 15:07:10] well with C you can set optimizations to -Og to make debug easier [2021-03-19 15:07:18] and then to -Os/3 for production [2021-03-19 15:10:19] did the code work after that change [2021-03-19 15:10:20] ? [2021-03-19 15:11:55] yes [2021-03-19 15:12:03] cool [2021-03-19 15:12:16] and you can make scan and get no bugs? [2021-03-19 15:15:50] → Zarutian_HTC joined (~bj@173-133-17-89.fiber.hringdu.is) [2021-03-19 15:18:22] no `scan-build` in openbsd base, and I don't have enough space to install llvm on this box [2021-03-19 15:20:07] aha [2021-03-19 15:20:10] ok nvm that then :) [2021-03-19 15:21:37] mark4: when I deploy a new install I'll setup a bigger disk and let you know how it goes, won't be for a while though [2021-03-19 15:23:12] thats ok, i have a lot to figure out yet, like maybe i have to hard code the key escape sequences for all terminals for shift cursor up, shift cursor down, shift home, shift end... [2021-03-19 15:23:59] and you can use any combination of control shift and alt on any key and get different key sequences for each and every terminal will give different results [2021-03-19 15:24:03] which is dumb [2021-03-19 15:24:29] contorl X, shit control X, alt control X, shift alt control X... all different sequences returned [2021-03-19 15:24:47] all different sequences returned on all possible terminals.... MAYBE [2021-03-19 15:30:26] ⇐ hosewiejacke quit (~hosewieja@i5C742F7A.versanet.de): Remote host closed the connection [2021-03-19 15:30:46] I'm happy I can avoid all of that [2021-03-19 15:33:47] :) [2021-03-19 15:34:08] just link to libncurses [2021-03-19 15:37:37] no, i just don't build tui's [2021-03-19 15:41:46] :) [2021-03-19 15:45:57] so, biden trips up 3 times walking up the stairs of af1. i think it might well actually be president harris soon [2021-03-19 15:46:05] just a guess [2021-03-19 16:07:48] ⇐ f-a quit (~f-a@151.38.142.44): Ping timeout: 246 seconds [2021-03-19 16:09:42] → f-a joined (~f-a@151.68.211.255) [2021-03-19 16:10:45] ⇐ gravicappa quit (~gravicapp@h37-122-125-6.dyn.bashtel.ru): Ping timeout: 264 seconds [2021-03-19 16:49:12] ⇐ f-a quit (~f-a@151.68.211.255): Quit: leaving [2021-03-19 17:00:08] * jess → JESS [2021-03-19 17:07:41] meh, they'll keep up the charade for as long as possible [2021-03-19 17:08:10] but what do i know? every time i think "they won't do that, the optics would be too bad", they always surprise me [2021-03-19 17:08:53] lol [2021-03-19 17:09:19] he might be a senile old goat but i think his voter base is even more so [2021-03-19 17:12:14] * JESS → jess [2021-03-19 17:24:32] I think that Democrat eleet thrusting Hillary in front of Bernie got many younger peeps disinterested in politics [2021-03-19 17:25:30] and I say that as an Icelander with no or little interst in USA politics [2021-03-19 17:26:53] :) [2021-03-19 17:28:47] too concerned about the volcano brewing under your feet to pay attention to US drama? [2021-03-19 17:29:29] cmtptr: no and besides it seems to be simmering down [2021-03-19 17:29:45] famous last words [2021-03-19 17:30:57] hope not lol. we cant afford to lose forth coders :) [2021-03-19 17:31:02] nope, the geologist on the news this evening said that the propability of an erruption has gone down considerably [2021-03-19 17:32:27] sat imagery using diff images between images taken at diffrent times show that the rate of rising has fallen to negative [2021-03-19 17:34:16] tremour soundings seem to indicate that the lava in the lava tube there has started to solidify [2021-03-19 17:35:29] and rate of small quakes in the area has dropped down to pre event levels [2021-03-19 17:35:46] if it did erupt do you think your country would change its name to lavaland [2021-03-19 17:36:17] or thawland? [2021-03-19 17:36:39] if there is an erruption going to happen at this area then it is most likely going to be a lava flow erruption [2021-03-19 17:37:45] not an explosive ash cloud erruption like Eyjafjallajökull was [2021-03-19 17:38:36] cmtptr: no [2021-03-19 17:39:02] inode: and definitly no [2021-03-19 17:40:56] no, the insight into USA politics is mainly due to one guy I know loosely in Utanríkisráðuneytinu (the ministry of foreign affares) [2021-03-19 18:05:41] inode: Iceland is green, Greenland is icy - but it got the annoying folks to move over there from Iceland, so the marketing worked. As a result I don't expect names to reflect reality there, ever ;-) [2021-03-19 18:11:14] → boru` joined (~boru@unaffiliated/boru) [2021-03-19 18:11:16] ⇐ boru quit (~boru@unaffiliated/boru): Disconnected by services [2021-03-19 18:11:19] * boru` → boru [2021-03-19 18:16:10] cmtptr: are you perchance a precog? it seems that erruption has started [2021-03-19 18:19:28] keep off the glowing grass :) [2021-03-19 18:19:47] you see it? or feel it? or news telling you about it? [2021-03-19 18:20:32] banner alert on rúv telly station channel [2021-03-19 18:21:18] patrickg: was vinland also based on a false promise? [2021-03-19 18:25:36] → Zarutian_HTC1 joined (~bj@173-133-17-89.fiber.hringdu.is) [2021-03-19 18:25:59] — Zarutian_HTC1 hates this wifi instability [2021-03-19 18:26:23] ⇐ Zarutian_HTC quit (~bj@173-133-17-89.fiber.hringdu.is): Read error: No route to host [2021-03-19 18:26:57] * Zarutian_HTC1 → Zarutian_HTC [2021-03-19 18:28:48] here is a news item with a webcam capture https://www.ruv.is/frett/2021/03/18/helstu-tidindi-eldgos-hafid-i-fagradalsfjalli [2021-03-19 18:33:44] ⇐ Zarutian_HTC quit (~bj@173-133-17-89.fiber.hringdu.is): Remote host closed the connection [2021-03-19 18:34:59] → Zarutian_HTC joined (~bj@173-133-17-89.fiber.hringdu.is) [2021-03-19 18:42:02] → Zarutian_HTC1 joined (~bj@173-133-17-89.fiber.hringdu.is) [2021-03-19 18:42:32] looks like a small one [2021-03-19 18:42:33] ⇐ Zarutian_HTC quit (~bj@173-133-17-89.fiber.hringdu.is): Read error: Connection reset by peer [2021-03-19 19:16:24] ⇐ rixard quit (~rixard@158.174.122.239): [2021-03-19 19:41:02] — Zarutian_HTC1 watches https://m.youtube.com/watch?v=_AdBcTMHG0Q and disagrees [2021-03-19 19:41:17] * Zarutian_HTC1 → Zarutian_HTC [2021-03-19 19:42:41] failed a lot, were expensive even though the electronic ballast was cheap shit, took forever to get to useable brightness [2021-03-19 19:43:41] and their sound was irritating as hell [2021-03-19 19:43:55] low volume high frequency hiss [2021-03-19 19:45:02] and do not get me started on how bad the light spectra (not temperture _specta_) these things had [2021-03-19 19:45:03] → rixard joined (~rixard@158.174.122.239) [2021-03-19 20:42:56] ⇐ tech_exorcist quit (txrcst@gateway/shell/hashbang/x-ibpmdcpyfyflvlfu): Quit: tech_exorcist [2021-03-19 20:49:09] ⇐ Zarutian_HTC quit (~bj@173-133-17-89.fiber.hringdu.is): Remote host closed the connection [2021-03-19 20:52:21] → Zarutian_HTC joined (~bj@173-133-17-89.fiber.hringdu.is) [2021-03-19 21:02:36] Zarutian_HTC, no, not a precog, everybody knows volcanos tend to erupt on fridays [2021-03-19 21:24:32] → dave0 joined (~davezero@069.d.003.ncl.iprimus.net.au) [2021-03-19 21:25:39] thats a lava flow not dust! [2021-03-19 21:25:47] no grounded aircraft :) [2021-03-19 21:35:53] → really3 joined (~justafrie@107.152.102.135) [2021-03-19 21:42:31] ⇐ Zarutian_HTC quit (~bj@173-133-17-89.fiber.hringdu.is): Remote host closed the connection [2021-03-19 21:54:19] i love forth [2021-03-19 21:59:13] what's your favorite forth word [2021-03-19 21:59:28] mine is probably + [2021-03-19 22:36:13] → boru` joined (~boru@unaffiliated/boru) [2021-03-19 22:36:16] ⇐ boru quit (~boru@unaffiliated/boru): Disconnected by services [2021-03-19 22:36:19] * boru` → boru [2021-03-19 22:52:33] ⇐ really3 quit (~justafrie@107.152.102.135): Remote host closed the connection [2021-03-19 23:24:32] ⇐ sts-q quit (~sts-q@212.53.219.143): Ping timeout: 240 seconds [2021-03-19 23:37:25] → sts-q joined (~sts-q@91.200.108.215) [2021-03-19 23:45:01] → _whitelogger_ joined (~whitelogg@uruz.whitequark.org)