rapidyaml VS halflife

Interesting, I hadn't come across extism before. How hard would it be to package https://github.com/biojppm/rapidyaml in this way? (And do you have a extism for dummies guide?)

The inability, or brittleness, to embed NUL bytes into the string, for once. Zeroed bytes can be valid as an internal bytes of a longer encoded character. And the inefficiency of tempting every caller to rederive the string length on every use, leading to such bugs as quadratic parsing behavior with sscanf. The extra register for an explicit length is a very minute price to pay compared to that.

Although you still have the other problem of sscanf, where read times can become quadratic.

You are really simplifying that issue. A lot of it has to be how the implementation of sscanf works and it's super easy to abuse by complete accident when a lot of data needs to be read and parsed to correct values. See more here: https://github.com/biojppm/rapidyaml/issues/40

Leading to eye-rolling problems like these: https://github.com/biojppm/rapidyaml/issues/40

It's a part of C++ project https://github.com/ValveSoftware/halflife

I wonder if this is something you can amend in the actual code here: https://github.com/ValveSoftware/halflife

I know the most known issue about overbright on github already states that they will not fix it, but that was from 2013 and thoughts about overbright issue could've changed since then. Plus I am running HL on linux and this issue Infuriates me since I'm stuck using the OpenGL renderer (which is the only renderer that has this issue). We've known that valve really likes their linux oriented approach, and plus we know they love their Deckies that they updated HL2 with fixes and QoL stuff, what's stopping them from fixing overbright?

More info on texture scaling: https://github.com/ValveSoftware/halflife/issues/1650

Funnily enough, on Half-Life 1 engine-based games (i.e. the engine that came before HL2 - on which Team Fortress 2 runs; such as Counter-Strike 1.6), a different allocator problem exists -- glibc's malloc() just decides to fail miserably[0] on some setups.

[0] https://github.com/ValveSoftware/halflife/issues/3158

I guess you have to either modify the code https://github.com/ValveSoftware/halflife/blob/master/dlls/hgrunt.cpp

The original Half Life, including goldsrc, is source-available: https://github.com/ValveSoftware/halflife

And in fact even their Half-Life 1 bugtracker on GitHub is policed: https://github.com/ValveSoftware/halflife/issues