D issues are now tracked on GitHub. This Bugzilla instance remains as a read-only archive.
Issue 3458 - int fsync(int) commented out in core.sys.posix.unistd
Summary: int fsync(int) commented out in core.sys.posix.unistd
Status: RESOLVED FIXED
Alias: None
Product: D
Classification: Unclassified
Component: druntime (show other issues)
Version: D2
Hardware: All Linux
: P2 normal
Assignee: Sean Kelly
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-30 19:01 UTC by Leandro Lucarella
Modified: 2015-06-09 01:26 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Leandro Lucarella 2009-10-30 19:01:37 UTC 
I don't know why, but the POSIX function fsync is commented out in the core.sys.posix.unistd module. Same for fdatasync().

Is there any reason for that?
Comment 1 Sean Kelly 2009-10-30 21:48:58 UTC 
It's an optional feature--declarations in POSIX headers are divided into labeled groups--and in the interest of time I've added them as needed.  Once I check that these functions are available on Linux and OSX I'll see about adding declarations for them.
Comment 2 Leandro Lucarella 2009-10-31 21:32:28 UTC 
I think fsync() is pretty common in all posix OSs, and it's essential to do any crash-resistant I/O.
Comment 3 Sean Kelly 2009-12-05 20:43:33 UTC 
Fix is in r210.
Comment 4 Leandro Lucarella 2009-12-08 13:33:30 UTC 
http://www.dsource.org/projects/druntime/changeset/210

Thanks
Comment 5 Walter Bright 2009-12-31 11:19:44 UTC 
Fixed dmd 2.038