Standardise ASM include path slash use #431

New Issue

2026-04-20T07:45:28Z

ace-dent commented

2026-04-20 07:45:28 +00:00

FASM on Windows supports both forward- and back-slashes as path separators. Forward slashes should be preferred.
include 'example/good' -vs- include 'example\bad'.

In FASM strings, the backslash can act as an escape character in some contexts. Forward slashes avoid this entirely and are portable across platforms, and match our tupfiles. BONUS: Makes searching for file usage more consistent! (e.g. git grep "example/good")

Add this rule to Kernel style documents, including the wiki and elsewhere(?)
Update the CI Python script for Kernel style checking.
Update all assembly files.

FASM on Windows supports both forward- and back-slashes as path separators. Forward slashes should be preferred. `include 'example/good'` -vs- `include 'example\bad'`. In FASM strings, the backslash can act as an escape character in some contexts. Forward slashes avoid this entirely and are portable across platforms, and match our tupfiles. BONUS: Makes searching for file usage more consistent! (e.g. `git grep "example/good"`) - [ ] Add this rule to Kernel style documents, including the [wiki](https://wiki.kolibrios.org/wiki/Style) and elsewhere(?) - [ ] Update the CI Python script for Kernel style checking. - [ ] Update all assembly files.

ace-dent added the

labels 2026-04-20 07:45:28 +00:00

ace-dent commented

2026-04-20 07:45:54 +00:00