@cazaugg@__phantomderp but double action. first in writing then in deleting. maybe conjure up the response in the head, close your eyes, flush it out the toilet and never respond?
@_trish_07 apart from all the comments, tell me what’s the point in using non-automatic static vars in an entrypoint? You ask for storing x on the stack that remains after main() has returned to its caller. And you can’t do anything beneath main() down the call stack. Why?
@yutongwu111140 the syntax has remained largely the same since the dinosaurs. The wg14 committee is more focused on other things than inlining asm syntax. it has been “character-string-literal” since the dawn of time.
@proffleon @ZuhaibHanfi Question is still relevant. Renounced C “experts” don’t recommend C anymore for new projects to be built from the ground up. Purely out of legacy and maintainability, and “grep-bility” that code sources don’t pivot. One aspect is that it will disturb the working devs’ workflow.
@emperornintri @ZuhaibHanfi The more you drag along the curve to the right, the more skeptical you get in what to use and how you get to use the things you took for granted. Being a “high level” language, and given you compile unoptimised, it relatively straightforward to predict what’s going to happen. but
@mustafa_kh4n C is largely prevalent solely and largely out of legacy and the fact that it’s had the time to mature over time. Although nothing has changed, but devs have. The amount of experience people have with C is disproportional to anything else. But start new projects in other langs.
@msc1979@BobPritchett@prasenx I don’t get it how you find it ”hard” to understand. It only requires knowledge of what goes into the leading part some special static char then into the domain. You have heard of quantifiers in middle school language class. What’s the problem?
@navyasreemn You should have posted it as a poll across some major compilers as decently unpopular and esoteric compilers compiled code won’t run on production. Because that’s what you __use__ rather than play with that matters.
@oisyn@wheeldev if the alloc'd block is **only** filled with zero bits and is interpreted as a struct, and we memset some literal all through the block, each field is set byte-by-byte.
If value is nonzero, the bit pattern of the literal is repeated equal to the size of the type.
@oisyn@wheeldev ISO C doesn’t define a null pointer, yes but NULL (the macro) is free-floating. The expansion of NULL (even if it contains zero) is handed to the compiler to convert to implementation-specific bit pattern of the null pointer constant. So cmp to literal 0 in pointer context is ok
@RuiCarrilho5@tsoding “Exceptional” would turn out a little bit less than that. Old code is reverberated in many circles and eventually, inevitably and invariably cracked (because holes in every code). Software doesn’t age, but minds do.
@vaxryy it’s C++, therefore unreadable. Written in hungarian convention. Will only build for C++23 (no guarding against __cplusplus). DWM only using x11 API is much more readable and easier to patch.
@arundsharma@sunbains You can refer to $src/src/kv/KVStore.h in the source tree that exposes sort of the KV interface. It’s C++, therefore unreadable so not sure if that’s what you are looking for.
Build it in the top level, and a subbuild should contain libleveldb.a. But class KVStore should be it.