This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[PATCH 0/3] libio: POSIX compliance fmemopen


Hi all,


This is a take 2 of the fmemopen modification to make it POSIX compliance.
As before it focus on addressing the bugs:

fmemopen_seek() incorrectly inverses seek offset when using SEEK_END
  https://sourceware.org/bugzilla/show_bug.cgi?id=14292
fmemopen does not honor append mode
  https://sourceware.org/bugzilla/show_bug.cgi?id=13152
fmemopen streams fail to read eof
  https://sourceware.org/bugzilla/show_bug.cgi?id=13151
fmemopen returns NULL when len=0
  https://sourceware.org/bugzilla/show_bug.cgi?id=11216
fmemopen(buf,size,"w+b") isn't binary
  https://sourceware.org/bugzilla/show_bug.cgi?id=12836
fseek(..., 0, SEEK_END) doesn't work as it should on fmemopen's FILE
  https://sourceware.org/bugzilla/show_bug.cgi?id=6544

Current fmemopen POSIX definition is:

http://pubs.opengroup.org/onlinepubs/9699919799/functions/fmemopen.html

Previous patches should be ignored. Difference from previous RFC patches set are:

* Now that POSIX relaxed the specification for zero length buffers [1] input,
  this implementation does not return NULL/EINVAL anymore.

* I have added more internal testing on tst-fmemopen2 to check for NULL
  and 0 length buffer.

* I have finished the abilist check files.


[1] http://austingroupbugs.net/view.php?id=818


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]