# Bring your own MAX_PATH_BYTES · gitcafe/zig

[View on GitCafe](https://git.cafe/gitcafe/zig/commit/37a1028b6e894881b85feb3d8555cacfabbc45a2)

Repository: [gitcafe/zig](https://git.cafe/gitcafe/zig)

Visibility: public

Requested revision: 37a1028b6e894881b85feb3d8555cacfabbc45a2

Requested commit: 37a1028b6e894881b85feb3d8555cacfabbc45a2

Commit: 37a1028b6e894881b85feb3d8555cacfabbc45a2

Tree: f2b791659264177773eac6b27458ac170bedb765

Author: mason1920

Committer: Veikka Tuominen

## Message

```
Bring your own MAX_PATH_BYTES

Previous to #7082, users could overwrite PATH_MAX in the root file to support std.os.toPosixPath, permitting the "bring your own operating system" layer to implement the POSIX API for opening files. Unfortunately that is no longer the case.

This commit intends to fix what is arguably a regression from 0.7 in a way that doesn't break any code targeting 0.8.0, making it suitable to be included in a 0.8 patch release.
However in a future release that permits breaking changes, I am of the opinion that it would be beneficial to overwrite the value, even for "supported" operating systems. Same for all the other POSIX/BYOOS functions and values. However this is beyond the scope of this commit. Further discussion of this will be made into an issue in due time.
```

## Parents

- [e006281d79a31e10bdbc07b3e33427d719ec01df](https://git.cafe/gitcafe/zig/commit/e006281d79a31e10bdbc07b3e33427d719ec01df?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zig/tree/37a1028b6e894881b85feb3d8555cacfabbc45a2?format=markdown)