Issue 123693 - const type qualifier on return type has no effect
Summary: const type qualifier on return type has no effect
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: 4.0.1
Hardware: All All
: P4 Normal (vote)
Target Milestone: 4.1.0
Assignee: hdu@apache.org
QA Contact:
URL:
Keywords:
Depends on:
Blocks: 122766
  Show dependency tree
 
Reported: 2013-11-15 16:05 UTC by hdu@apache.org
Modified: 2014-04-01 12:28 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

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 hdu@apache.org 2013-11-15 16:05:35 UTC 
The C++ standard requests that non-class type rvalues are never const-qualified. All compilers still allow it but warn about the confusing construct and ignore it.
Comment 1 SVN Robot 2013-11-18 09:45:33 UTC 
"hdu" committed SVN revision 1542958 into trunk:
#i123693# WaE: const type qualifier ignored on return value
Comment 2 hdu@apache.org 2013-11-18 10:06:15 UTC 
The commit above fixed a lot of noisy warning (117 times on LX64). Mostly because the often-used zformat header file is used a lot and its problems were reported every time it was included.
Comment 3 SVN Robot 2014-01-08 09:10:28 UTC 
"hdu" committed SVN revision 1556469 into trunk:
#i123693# WaE: const type qualifier ignored on return value
Comment 4 hdu@apache.org 2014-01-08 09:14:23 UTC 
And the commit above fixes another 70 warnings, all caused by the one method OOXMLStream::getIDForXNoteStream() requesting a nonsensical "const" for its integer return value.
Comment 5 hdu@apache.org 2014-04-01 12:28:50 UTC 
Closing the resolved issue.