Opened 10 years ago
Last modified 4 years ago
#12049 assigned enhancement
Haiku Book should warn about area_delete changes
Reported by: | Barrett | Owned by: | nobody |
---|---|---|---|
Priority: | low | Milestone: | R1.1 |
Component: | Documentation | Version: | R1/Development |
Keywords: | HaikuBook | Cc: | |
Blocked By: | Blocking: | ||
Platform: | All |
Description (last modified by )
A comment in the current virtual memory code states that differently from BeOS, in Haiku it's not possible to delete an area_id created by another team, this should be cleared out in the Haiku Book.
Change History (5)
comment:1 by , 10 years ago
Description: | modified (diff) |
---|---|
Summary: | BeBook should warn about area_delete changes → Haiku Book should warn about area_delete changes |
comment:2 by , 10 years ago
I've seen in the bebook lines stroked for deprecated API, i've think that we can stroke in the bebook delete_area section the phrases "Currently, anybody can delete any area—the act isn't denied if, for example, the area_id argument was created by another application." and "Until then, try to", but maybe i'm wrong and those lines were already stroked.
comment:3 by , 8 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:4 by , 5 years ago
Keywords: | HaikuBook added |
---|
comment:5 by , 4 years ago
Milestone: | R1 → R1.1 |
---|
Note:
See TracTickets
for help on using tickets.
We aren't allowed to modify the Be Book, but we can (and should) add a note about this to the Haiku Book.