OpenBSD malloc has many peculiarities:
Yes, I know. I’ve seen this and other articles about OpenBSD malloc before. Every malloc has “many peculiarities”, really; otherwise what would be the differences between them?
Did you have a particular point in linking this article here?
The differences in usage and performance objectives.
The article’s link shows that there is not much documentation for OpenBSD malloc on the OpenBSD website. Haiku should probably provide more objective and clear documentation than OpenBSD has, in addition to code adaptations and removals.
The documentation is mostly in the source code and other articles. Why would we need to provide more documentation than OpenBSD here?
And what do you mean by “differences in usage and performance objectives”? Every malloc has different ones, so of course OpenBSD’s aren’t the same as other’s…
I mean documentation, which is not clearly displayed. I noticed that gsoc participants had a great deal of difficulty finding documentation or identifying where this source code base should be to start. This applies to any project they want to start, whether native or a port.
That would be it, to meet Haiku’s needs, there would probably be performance changes, which OpenBSD does not have