#5333 closed enhancement (no change required)
SEM_VALUE_MAX not defined
| Reported by: | kaliber | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | System/POSIX | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
I'm not sure it's in the POSIX standard http://www.opengroup.org/onlinepubs/000095399/functions/sem_open.html but it's widely used http://www.google.com/codesearch?hl=en&lr=&q=SEM_VALUE_MAX&sbtn=Search
Change History (4)
comment:1 by , 15 years ago
comment:2 by , 10 years ago
| Milestone: | R1 → Unscheduled |
|---|
Move POSIX compatibility related tickets out of R1 milestone (FutureHaiku/Features).
comment:3 by , 6 years ago
| Resolution: | → no change required |
|---|---|
| Status: | new → closed |
HaikuPorts has not run into any applications at all that needed this, so the work to add it is probably not worth the time.
comment:4 by , 5 years ago
| Milestone: | Unscheduled |
|---|
Remove milestone for tickets with status = closed and resolution != fixed
Note:
See TracTickets
for help on using tickets.
The macro
SEM_VALUE_MAXdoes not *need* to be defined.sysconfig(_SC_SEM_VALUE_MAX)should be used in portable code. Nonetheless it doesn't hurt to define it. Along with a whole bunch of other limit macros.