Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Header files in a different directory #453

Open
jordanflitter opened this issue Jan 30, 2025 · 1 comment
Open

Header files in a different directory #453

jordanflitter opened this issue Jan 30, 2025 · 1 comment
Labels
context: v4-prep This issue regards changes to the v4-prep branch status: requires discussion Issue requiring some time to process and discuss type: refactor Code refactoring / restyling for internal benefit

Comments

@jordanflitter
Copy link

Right now the header files of v4 are at the same directory of the C files, making the src directory a bit hard to navigate as it currently contains 64 files. Alternatively, we can do something similar as in CLASS, and put all the header files in an "include" directory (see https://github.com/lesgourg/class_public/tree/master/include vs. https://github.com/lesgourg/class_public/tree/master/source).

@jordanflitter jordanflitter added context: v4-prep This issue regards changes to the v4-prep branch type: refactor Code refactoring / restyling for internal benefit labels Jan 30, 2025
@daviesje
Copy link
Contributor

daviesje commented Feb 3, 2025

I'm sure there's a lot of debate and personal preference about the organisation of packages, and while I'm open to suggestions, I prefer the layouts where the .c/.h pairs are kept together, and subdirectories are made based on the purpose of the files. We should definitely talk about the folder layout before the release of v4 though.

@daviesje daviesje added the status: requires discussion Issue requiring some time to process and discuss label Feb 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
context: v4-prep This issue regards changes to the v4-prep branch status: requires discussion Issue requiring some time to process and discuss type: refactor Code refactoring / restyling for internal benefit
Projects
None yet
Development

No branches or pull requests

2 participants