Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


Hello,

Cppcheck reports this :
[formmetadata.cxx:169] -> [formmetadata.cxx:169]: (style) Same expression on
both sides of '|'

Here's the line :
DEF_INFO_4( INSERTONLY,        DATAENTRY,          DATAENTRY,        
FORM_VISIBLE, DATA_PROPERTY, COMPOSEABLE, COMPOSEABLE ),

If we look at the definition of the macro :
#define DEF_INFO_4( ident, uinameres, helpid, flag1, flag2, flag3, flag4 ) \
    DEF_INFO( ident, uinameres, helpid, PROP_FLAG_##flag1 |
PROP_FLAG_##flag2 | PROP_FLAG_##flag3 | PROP_FLAG_##flag4 )

the pb the presence of "COMPOSEABLE" twice.

Searching in git history, I found the commit
0aaf3fb6af9dfa91b2597894930fdc8b23041308
which replaced this line (there are others) :
DEF_INFO_2( INSERTONLY,        DATAENTRY,          DATAENTRY,        
FORM_VISIBLE, DATA_PROPERTY ),
by
this one :
DEF_INFO_4( INSERTONLY,        DATAENTRY,          DATAENTRY,        
FORM_VISIBLE, DATA_PROPERTY, COMPOSEABLE, COMPOSEABLE ),

So it could be this :
DEF_INFO_3( INSERTONLY,        DATAENTRY,          DATAENTRY,        
FORM_VISIBLE, DATA_PROPERTY, COMPOSEABLE),

but it could also be DEF_INFO_4 with 1 extra property or even DEF_INFO_5
with 2 extra properties.

Any idea ?

Julien.

--
View this message in context: 
http://nabble.documentfoundation.org/Same-expression-on-both-sides-of-tp3731097p3731097.html
Sent from the Dev mailing list archive at Nabble.com.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.