Movatterモバイル変換


[0]ホーム

URL:



This page is a snapshot from the LWG issues list, see theLibrary Active Issues List for more information and the meaning ofTC1 status.

158. Underspecified semantics forsetbuf()

Section: 31.6.3.5.2[streambuf.virt.buffer]Status:TC1Submitter: Dietmar KühlOpened: 1999-07-20Last modified: 2016-01-28

Priority:Not Prioritized

View all otherissues in [streambuf.virt.buffer].

View all issues withTC1 status.

Discussion:

The default behavior ofsetbuf() is described only for thesituation thatgptr() != 0 && gptr() != egptr():namely to do nothing. What has to be done in other situations is not described although there is actually only one reasonableapproach, namely to do nothing, too.

Since changing the buffer would almost certainly mess up mostbuffer management of derived classes unless these classes do itthemselves, the default behavior ofsetbuf() should always beto do nothing.

Proposed resolution:

Change 31.6.3.5.2[streambuf.virt.buffer], paragraph 3, Default behavior,to: "Default behavior: Does nothing. Returns this."


[8]ページ先頭

©2009-2026 Movatter.jp