d545ad17ce
Previously, __haiku_init_before was a symbol that was included in each (shared) object, and so it could be used to determine what one we were in. Now, there are no such universal symbols that are declared private to only the object, so we have to use a different approach. __func__ is defined as a const char* at the very beginning of every function it's used in, set to a string of the function name only, i.e., the arguments and return type are left off. So while including that is perhaps not quite optimal, in practice this definition is used extremely rarely (it was introduced by Haiku, and it is used in only 2 applications at all that I could find -- WebKit and Canna.) There really isn't any other way to get a pointer that we know for certain is within the current object besides this one without inserting one, but that really isn't merited just for this. (__builtin_return_address() has problematic semantics wrt. inlining, including linker-inlining.) So this will have to do.
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.
Contributing to our infrastructure
See Infrastructure.