Skip to content

Reorganize API #30

@johnpatek

Description

@johnpatek

The file structure and API layout should be updated to be more intuitive. Without breaking the API, things like utilities and platform specific code should have a clear and logical location within the codebase. Within files, a good general rule would be the following:

  • preprocessor and constants at the top
  • core classed and functions in the middle
  • convenience and utility code at the bottom

It is unclear how much of this can be done with the existing header structure, as there are things like page.hpp, which has page offset/alignment related functions, but also includes access mode definitions and some platform specific code.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions