57672294e9
After this patch "UnitTester BDirectory" passes. Most of this test suite already documented the differences in behavior between BeOS R5 and Haiku. I verified whether these comments were accurate and removed the cases which handle BeOS specific behavior. Most of the differences are just Haiku using more specific errors: * Initializing BDirectory with an entry that is not a directory results in B_NOT_A_DIRECTORY. * There is obviously no /boot/beos. Use /boot/system for this test instead. BDirectory::IsRootDirectory returns true for this path since it is the root of the system package. * Initializing to child path "" results in B_ENTRY_NOT_FOUND instead of successful initialization with B_OK only to later return B_BAD_VALUE if the BDirectory is used. * BDirectory::Find(NULL, BEntry*) doesn't touch the BEntry parameter since the provided path is NULL, where BeOS R5 will set the BEntry's status to B_BAD_VALUE. * Clean up -Wparentheses warnings for assertions of the form CPPUNIT_ASSERT(path == existingSub == B_OK), which is another way of saying path != existingSub. This is because the path ends up being a normalied path, but the input path is not. For example /tmp/existing-dir becomes /boot/system/cache/tmp/existing-dir. I verified that this is the same behavior as BeOS, and then added some normalized paths to compare against. Change-Id: I5125ef221fba92793959efead96d7daaa181a119 Reviewed-on: https://review.haiku-os.org/c/haiku/+/2826 Reviewed-by: Adrien Destugues <pulkomandy@gmail.com>
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.