| ▲ | ntoslinux 8 hours ago | |||||||
What is the reason for the weird `{ code };` blocks everywhere and is the below code machine generated? ```c ((PageSize) (chunk->pageSize - ((PageSize) ((PageSize) ((PageSize) (sizeof(Page) + (sizeof(struct _Block))) + (PageSize) ((sizeof(double)) - 1u)) & ((PageSize) (~((PageSize) ((sizeof(double)) - 1u)))))) - ((PageSize) ((PageSize) ((PageSize) ((sizeof(FreeBlock) + sizeof(PageSize))) + (PageSize) (((((sizeof(double)) > (4)) ? (sizeof(double)) : (4))) - ``` | ||||||||
| ▲ | mzajc 7 hours ago | parent | next [-] | |||||||
Worse yet, there's several places with empty code blocks, eg. [0] and [1]. Even without that, the formatting contains so much unnecessary whitespace, newlines, casts, etc; I'm not sure why, given the already massive source file. How do you even fit [2] on a screen? [0]: https://github.com/xtellect/spaces/blob/422dbba85b5a7e9a209a... [1]: https://github.com/xtellect/spaces/blob/422dbba85b5a7e9a209a... [2]: https://github.com/xtellect/spaces/blob/422dbba85b5a7e9a209a... | ||||||||
| ▲ | bitbasher 8 hours ago | parent | prev [-] | |||||||
There's a lot of code in the file that is questionable to say the least. There are unnecessary blocks ( { ... }; ) of code with unnecessary semicolons that don't serve any logical purpose. My hunch tells me it may be the result of macro-expansion in C (cc -E ...), etc. So it's likely there's a larger code base with multiple files and they expanded it into a one large C file (sometimes called an amalgamation build) and called it a day. By they, I mean the OP, a script or an AI (or all three). | ||||||||
| ||||||||