adding wxFALLTHROUGH where until now we had comments, allows for code-analysis support
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@76399 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
@@ -92,7 +92,7 @@ wxChar wxTextInputStream::NextChar()
|
||||
// loop iteration we shouldn't be able to decode 2 or more of
|
||||
// them with an extra single byte, something fishy is going on
|
||||
wxFAIL_MSG("unexpected decoding result");
|
||||
// fall through nevertheless and return at least something
|
||||
wxFALLTHROUGH;// fall through nevertheless and return at least something
|
||||
|
||||
case 1:
|
||||
// we finally decoded a character
|
||||
@@ -457,7 +457,7 @@ void wxTextOutputStream::WriteString(const wxString& string)
|
||||
|
||||
default:
|
||||
wxFAIL_MSG( wxT("unknown EOL mode in wxTextOutputStream") );
|
||||
// fall through
|
||||
wxFALLTHROUGH;
|
||||
|
||||
case wxEOL_UNIX:
|
||||
// don't treat '\n' specially
|
||||
|
Reference in New Issue
Block a user