Section: 30.5.4 [fpos] Status: NAD Submitter: Matt Austern Opened: 1997-12-15 Last modified: 2016-08-08
Priority: Not Prioritized
View all other issues in [fpos].
View all issues with NAD status.
Table 88, in I/O, is too strict; it's unimplementable on systems
where a file position isn't just an offset. It also never says just
fpos<> is really supposed to be. [Here's my summary, which
Jerry agrees is more or less accurate. "I think I now know what
the class really is, at this point: it's a magic cookie that
mbstate_t and a file position (possibly represented as
fpos_t), it has syntactic support for pointer-like arithmetic, and
implementors are required to have real, not just syntactic, support
for arithmetic." This isn't standardese, of course.]
Not a defect. The LWG believes that the Standard is already clear, and that the above summary is what the Standard in effect says.