Re: [SOLVED] Re: Question about operator = overloaded in reportdesign module

2013-01-03 Thread Michael Stahl
On 02/01/13 10:11, Lionel Elie Mamane wrote: > C++11 has a specific syntax to achieve mostly the same effect more > cleanly: > > OXMLCell& operator =(const OXMLCell&) = delete; > > That's slightly better since it tells the compiler that this class > should have *no* assignment operator. So any

Re: [SOLVED] Re: Question about operator = overloaded in reportdesign module

2013-01-03 Thread Lubos Lunak
On Wednesday 02 of January 2013, Lionel Elie Mamane wrote: > C++11 has a specific syntax to achieve mostly the same effect more > cleanly: > > OXMLCell& operator =(const OXMLCell&) = delete; > > That's slightly better since it tells the compiler that this class > should have *no* assignment opera

Re: [SOLVED] Re: Question about operator = overloaded in reportdesign module

2013-01-02 Thread Lionel Elie Mamane
On Sun, Dec 30, 2012 at 09:58:30PM +0100, Julien Nabet wrote: > On 30/12/2012 21:48, Markus Mohrhard wrote: >>>Cppcheck reported this: >>>[reportdesign/source/filter/xml/xmlComponent.hxx:37]: (style) >>>'OXMLComponent::operator=' should return 'OXMLComponent&'. >>>[reportdesign/source/filter/xml/x

[SOLVED] Re: Question about operator = overloaded in reportdesign module

2012-12-30 Thread Julien Nabet
On 30/12/2012 21:48, Markus Mohrhard wrote: Hey, Cppcheck reported this: [reportdesign/source/filter/xml/xmlComponent.hxx:37]: (style) 'OXMLComponent::operator=' should return 'OXMLComponent&'. [reportdesign/source/filter/xml/xmlFunction.hxx:41]: (style) 'OXMLFunction::operator=' should return