fc03b45a71
The standardized version of readv() and writev() take an int as the third parameter. Arguably a size_t makes more sense, but the standardization bodies decided otherwise. The non-standard functions of readv_pos() and writev_pos() have been updated for consistency. The corresponding _kern_readv() and _kern_writev() internal functions continue to take the size_t parameter. The ABI will not change, even though on 64 bit machines the size of the count parameter will change from 8 to 4 bytes. The actual use will be slightly different. Like with the size_t argument type, it will not be possible to give a count lower than 0. If the value is less than 0, then the B_BAD_VALUE/EINVAL error will be set. Change-Id: I949c8ed67dbc0b4e209768cbdee554c929fc242e Reviewed-on: https://review.haiku-os.org/c/haiku/+/3770 Reviewed-by: Jérôme Duval <jerome.duval@gmail.com> |
||
---|---|---|
3rdparty | ||
build | ||
data | ||
docs | ||
headers | ||
src | ||
.editorconfig | ||
.gitignore | ||
.gitreview | ||
configure | ||
Jamfile | ||
Jamrules | ||
lgtm.yml | ||
License.md | ||
ReadMe.Compiling.md | ||
ReadMe.md |
Haiku
Homepage | Mailing Lists | IRC Channels | Issue Tracker | API docs
Haiku is an open-source operating system that specifically targets personal computing. Inspired by the BeOS, Haiku is fast, simple to use, easy to learn and yet very powerful.
Goals
- Sensible defaults with minimal configuration required.
- Clean, clear, concise code.
- Unified desktop environment.
Trying Haiku
Haiku provides pre-built nightly images and release images. Haiku is compatible with a large variety of hardware, but in case you don't want to "take the plunge" and install Haiku on bare metal, you can install it on a virtual machine (VM) instead. If you've never used a VM before, you can follow one of the "Emulating Haiku" guides.
Compiling Haiku
See ReadMe.Compiling
.
Contributing
Haiku is a meritocratic open source project with a large variety of tasks. Even if you can't write code, you can still help! Haiku needs designers, (technical) writers, translators, testers... Get involved and help out!
Contributing code
If you're submitting a patch to us, please make sure you're following the patch submitting guidelines.
If you're having trouble finding something in the source tree, you can use one of our web-based source code browsers:
- https://xref.landonf.org/ (OpenGrok, provided by Landon Fuller)
- https://git.haiku-os.org/ (git, provided by Haiku, Inc.)
Contributing documentation
The main piece of documentation that still needs work are the API docs (found
in the tree at docs/user
). Just find an undocumented class, write
documentation for it, and submit a patch.
Contributing translations
See wiki:i18n.
Contributing software ports
See HaikuPorts.
Contributing to our infrastructure
See Infrastructure.