Ran
|
Files
114
|
Run time
5s
|
Badge
Embed ▾
README BADGES
|
travis-ci
<a href="https://github.com/gccxml/pygccxml/commit/a406ff56f">Fixes for type traits handling of cv-qualified array types cv-qualified arrays were not being handled correctly by type traits manipulations functions. For instance, 'int const[N]' would not be detected as 'const'. Similar problems existed for volatile qualified arrays too. There is a difference in behavior between GCCXML and CastXML for cv-qual arrays. GCCXML produces the following nesting of types: -> volatile_t(const_t(array_t)) while CastXML produces the following nesting: -> array_t(volatile_t(const_t)) For both cases, we must unwrap the types, remove const_t, and add back the outer layers. Prior to CastXML/CastXML#55 being fixed, CastXML would incorrectly generate default constructor definitions for types with const data members. This caused pygccxml to incorrectly flag such types as trivially constructible. These tests have now been fixed, and the tests are being executed conditionally only for GCCXML (which handles them correctly), or, if CastXML is being used, then for xml_output_version >= 1.138. gccxml places cv-qualifiers to the right of the array declarator in the decl_string. For instance, given the declaration 'int const[arr[42]', the decl_string from gccxml is 'int [42] const'. Combined type_traits_castxml.hpp and type_traits_gccxml.hpp into a single file - type_traits.hpp. Change-Id: I</a><a class="double-link" href="https://github.com/gccxml/pygccxml/commit/f5deaecf4">f5deaecf4</a>
8132 of 10135 relevant lines covered (80.24%)
0.8 hits per line
Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
---|