Oddbean

Yes C89 enforces declare before assign. They must be completely separate statements ';'. >and do you really need to explicitly state that a function has no parameters like that For C89 and -pedantic, yes. Some compilers even in C89 mode don't care, GCC will complain though. I think the Windows cl doesn't care though.

also with the file-level non-imperative declaration (though it does execute functions in var and init() in top to bottom order, that can be troublesome sometimes but it is what it is, and globals are bad mkay)

yeah, i was having a bad afternoon when suddenly somehow it seemed like the event store wasn't keeping tags but no... it wasn't decoding tags... and it seems i have retained the memory leak bug fix as well so i'm feeling very moisturised

yeah, it wasn't growing the arrays to fit what was being put into them still got another glitch in here somewhere, probably a regression... again a forever loop in the database query code lol idk even how it's happening, probably me putting the wrong direction <> in somewhere

i think i found it... i switched to collecting the found events in a map (key/value hash table) and i was checking the limit size based on the result variable which isn't populated until after all the event keys are retrieved i think this will fix it it's that kind of forever loop where your termination condition is incorrect and it keeps looping because the condition doesn't update to reflect the state of execution

btw, the point of using the maps is it allows me to automatically deduplicate in case of clients sending filters with repeating elements that yield the same event again... which probably can happen, so best to mitigate it