[haiku-bugs] Re: [Haiku] #2696: unimplemented functions
- From: "bonefish" <trac@xxxxxxxxxxxx>
- Date: Mon, 06 Dec 2010 17:03:39 -0000
#2696: unimplemented functions
--------------------------------+-----------------------------
Reporter: kaliber | Owner: axeld
Type: bug | Status: new
Priority: normal | Milestone: R1
Component: System/libroot.so | Version: R1/pre-alpha1
Resolution: | Keywords:
Blocked By: 2564 | Has a Patch: 0
Platform: All | Blocking:
--------------------------------+-----------------------------
Comment (by bonefish):
Replying to [comment:26 jprostko]:
> I just wanted to mention that several students for Google Code-in have
taken on this task to complete. Depending on how things go, I'll post
patches here for review prior to committing to trunk.
Great! Please take care not to add/change stuff that isn't actually
supported by the implementation.
deangenovski, thanks, that's a start. scottmc and umccullough are right,
though: Some headers don't define all the stuff required by POSIX
themselves, but include other headers that do (which is just fine), and
some headers are provided by the compiler. Moreover, POSIX requires dozens
of headers of which Haiku is definitely missing quite a few, and likely
has a good deal of headers that don't fully conform to the specification.
I think it would be best to organize the information either in a wiki or
in hierarchical tickets. I.e. one overview section/ticket listing all the
non-conforming/missing (and maybe even the conforming) headers, for each
header a section/ticket listing the defects in the header, and per defect
(or group of defects) a subsection/ticket detailing on them. As written
earlier IMO the best approach is to compile a complete list of headers
first and then iterate through them and add details. The second step can
be parallelized wonderfully.
--
Ticket URL: <http://dev.haiku-os.org/ticket/2696#comment:27>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
