Rachel
To wit on the above use case, our project's compiled archive binaries must match a specific SHA-sum, which means that the archives must be packed in a certain order. Historically,...
> an alternative approach would be to make custom_target use rsp files automatically. I do agree with @bruchar1 that it doesn't seem to make sense to automatically use rsp files,...
Offering support for a leading-args parameter I think makes more sense than expecting an underlying program to always interpret a response file via the same methodology. At least for my...
I don't like breaking the paradigm of the top-level folder split being src/include; embedding that deeper seems like a breach of C norms that isn't really worth it and is...
I don't mind the idea of, e.g., `src/(overlay/){battle_eng,battle_ui,battle_ai}` (`overlay` subfolder optionally omitted, depending on how the full structure looks).
I would like to propose the following structure, using a few example overlays for illustration. For brevity, only `include` is shown here, but `src` would follow the same structure. ```...
1. Command name styling: `PascalCase` (fine with `snake_case`) 2. Entry-point label styling: `PascalCase` (fine with `camelCase`) 3. Use local labels: No (gcc-incompatible means local labels are not tenable) 4. Within-subroutine...
We should also note that, technically speaking, labels are implicitly local in DS scripts; they're individual files within an archive, not a collection of scripts stitched together and then compiled.
We have no consensus on (4).
Closing in favor of #229