Remove superfluous parens Rename result variable to bytesWritten Sync() Unwrap ternary style fix (for consistency) * Shouldn't this return fCStatus instead of B_FILE ERROR? * BeBook says "returning B_OK on success and an appropriate error message otherwise." * Has returned B_FILE_ERROR since "it is accomplished ..." Rename result variable to bytesWritten (again) Remove superfluous space explictly cast status_t to ssize_t Remove superfluous parens, remove space, add newline Explicitly cast status_t to ssize_t (again) WriteAttrString() cleanup * rename error to result * rename sizeWritten to bytesWritten (consistency and clarity) * check if error cede from WriteAttr and cast to status_t * > not entirely style but functionaly same * if length is different then written return B_FILE_ERROR * > not a style change but a very minor functional change * add some comments Tiny documentation fix precede vars with \a More style fixes * Rename error to result * Put parens around conditional of ternary instead of whole thing * Compare against NULL explicitly * Don't set fCStatus here, we're going to set it in the calling function instead * > note that Unset() sets fCStatus to B_NO_INIT but that's ok 80 char limit style fix More style fixes and don't set fCStatus * remove superfluous parens * compare ref to NULL explicitly * > Also don't set fCStatus here since we will do that in calling function Unset() sets fCStatus to B_NO_INIT but that's ok Unwrap ternary style fix (consistency) Rename error to result (again)
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 OpenGrok servers:
- http://xref.plausible.coop/ (provided by Landon Fuller)
- http://code.metager.de/source/xref/haiku (provided by MetaGer)
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.