Kaydet (Commit) 514433a8 authored tarafından Markus Mohrhard's avatar Markus Mohrhard

export and fix pretty printers for calc unit tests

Change-Id: Ifa5d097e3c09fa0c96339b4eb6fd2be81516856d
üst 915303a7
...@@ -62,7 +62,7 @@ std::ostream& operator<<(std::ostream& rStrm, const ScRangeList& rList) ...@@ -62,7 +62,7 @@ std::ostream& operator<<(std::ostream& rStrm, const ScRangeList& rList)
std::ostream& operator<<(std::ostream& rStrm, const Color& rColor) std::ostream& operator<<(std::ostream& rStrm, const Color& rColor)
{ {
rStrm << "Color: R:" << rColor.GetRed() << " G:" << rColor.GetGreen() << " B: << rColor.GetBlue()"; rStrm << "Color: R:" << (int)rColor.GetRed() << " G:" << (int)rColor.GetGreen() << " B: " << (int)rColor.GetBlue();
return rStrm; return rStrm;
} }
......
...@@ -97,15 +97,15 @@ struct FileFormat { ...@@ -97,15 +97,15 @@ struct FileFormat {
// Printers for the calc data structures. Needed for the EQUAL assertion // Printers for the calc data structures. Needed for the EQUAL assertion
// macros from CPPUNIT. // macros from CPPUNIT.
std::ostream& operator<<(std::ostream& rStrm, const ScAddress& rAddr); SCQAHELPER_DLLPUBLIC std::ostream& operator<<(std::ostream& rStrm, const ScAddress& rAddr);
std::ostream& operator<<(std::ostream& rStrm, const ScRange& rRange); SCQAHELPER_DLLPUBLIC std::ostream& operator<<(std::ostream& rStrm, const ScRange& rRange);
std::ostream& operator<<(std::ostream& rStrm, const ScRangeList& rList); SCQAHELPER_DLLPUBLIC std::ostream& operator<<(std::ostream& rStrm, const ScRangeList& rList);
std::ostream& operator<<(std::ostream& rStrm, const Color& rColor); SCQAHELPER_DLLPUBLIC std::ostream& operator<<(std::ostream& rStrm, const Color& rColor);
std::ostream& operator<<(std::ostream& rStrm, const OpCode& rCode); SCQAHELPER_DLLPUBLIC std::ostream& operator<<(std::ostream& rStrm, const OpCode& rCode);
// Why is this here and not in osl, and using the already existing file // Why is this here and not in osl, and using the already existing file
// handling APIs? Do we really want to add arbitrary new file handling // handling APIs? Do we really want to add arbitrary new file handling
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment