# Bring your own MAX_PATH_BYTES · gitcafe/zig

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

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

Visibility: public

Requested revision: 939408289cd05ba2f3b90eb626a388b6a5c747c4

Requested commit: 939408289cd05ba2f3b90eb626a388b6a5c747c4

Commit: 939408289cd05ba2f3b90eb626a388b6a5c747c4

Tree: 4dadcf4c4a9b70f9b706d3ed3aaef9d0f1275883

Author: mason1920

Committer: Andrew Kelley

## 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

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

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