Databases
StackOverflow2013
Postsdbo
POtemplate specialization for CPPUnit isn't being used
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POtemplate specialization for CPPUnit isn't being used
    primarykey
    data
    text
    <p>If you've used CPPUnit before, you are probably aware of its <code>assertion_traits</code> class that is templatized to handle arbitrary types. This is what allows it to print the "actual" and "expected" values for non-string types when test cases fail. I have used this with success several times, but for one specific type it isn't working for me. Here is a partial declaration for my class, its parent's class, and some non-member operators (the whole thing is huge, plus my company won't let me post it):</p> <pre><code>class _declspec(dllexport) HWDBDateTime { public: HWDBDateTime(); HWDBDateTime(const HWDBDateTime&amp; other); HWDBDateTime&amp; operator=(const HWDBDateTime&amp; other); RWCString asString() const; RWCString asString(const char *format, const boost::local_time::time_zone_ptr pZone = STimeZone::GetServerTimeZone()) const; }; bool _declspec(dllexport) operator==(const HWDBDateTime&amp; dt1, const HWDBDateTime&amp; dt2); bool _declspec(dllexport) operator!=(const HWDBDateTime&amp; dt1, const HWDBDateTime&amp; dt2); bool _declspec(dllexport) operator&lt; (const HWDBDateTime&amp; dt1, const HWDBDateTime&amp; dt2); bool _declspec(dllexport) operator&lt;=(const HWDBDateTime&amp; dt1, const HWDBDateTime&amp; dt2); bool _declspec(dllexport) operator&gt; (const HWDBDateTime&amp; dt1, const HWDBDateTime&amp; dt2); bool _declspec(dllexport) operator&gt;=(const HWDBDateTime&amp; dt1, const HWDBDateTime&amp; dt2); class _declspec(dllexport) STimeStamp : public HWDBDateTime { public: STimeStamp(); STimeStamp(const STimeStamp&amp; other); STimeStamp(const HWDBDateTime&amp; other); explicit STimeStamp(double d); STimeStamp&amp; operator=(double d); operator double() const; }; </code></pre> <p>And here is my attempt at specializing the CPPUnit assertions class:</p> <pre><code>template &lt;&gt; struct CppUnit::assertion_traits&lt;STimeStamp&gt; { static bool equal( STimeStamp x, STimeStamp y ) { return x == y; } static std::string toString( STimeStamp x ) { return (const char *)x.asString(); } }; </code></pre> <p>I've tried it passing by value, as seen above, also passing const references, I've tried casting the values inside the functions to <code>HWDBDateTime</code> (since that's where the operators and <code>asString()</code> methods are defined), nothing seems to help. I've put it at the top of my test suite's CPP file, and I've put it into a master header file that contains project-wide assertion_traits specializations, such as one for RWCString that works flawlessly. Somehow, whenever a test case fails, it insists on printing out my time as a floating-point value (presumably a double; a specialization for double is built in to CPPUnit) -- this is why I made sure to include my to/from double conversion operators in the minimized code above.</p> <p>Is there something inherently wrong with what I'm doing? Does the specialization need to be present at a certain point in the compilation process, and maybe I just haven't found that point? Would this mythical point be per-translation-unit or per-project? I'm using VS2008.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USrmeador
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POtemplate specialization for CPPUnit isn't being used
      1. This table or related slice is empty.
      1. VTUpMod
    1. CODid you try to define the template with `const STimeStamp&`? I had a similar problem and that helped.
      singulars
      1. POtemplate specialization for CPPUnit isn't being used
      1. USrioki
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload