move our CStirng into a namespace to fix conflict with MFC

This commit is contained in:
Chris Danford
2005-12-09 19:15:31 +00:00
parent cffff7739b
commit dc35d10ee4
3 changed files with 6 additions and 3 deletions
+1 -1
View File
@@ -3,7 +3,7 @@
#include "EnumHelper.h"
#include "ThemeManager.h"
CString GetThemedString( CCStringRef sClass, CCStringRef sValue )
CString GetThemedString( const CString &sClass, const CString &sValue )
{
return THEME->GetMetric( sClass, sValue );
}
+4
View File
@@ -305,6 +305,8 @@ typedef char* PSTR;
// the more portable, standard way of doing things, while the other is the
// non-standard, but often significantly faster Visual C++ way.
// =============================================================================
namespace StdString
{
// -----------------------------------------------------------------------------
// sslen: strlen/wcslen wrappers
@@ -1303,6 +1305,8 @@ struct StdStringEqualsNoCaseA
// }
//}
} // namespace StdString
#if defined(_MSC_VER) && (_MSC_VER > 1100)
#pragma warning (pop)
#endif
+1 -2
View File
@@ -134,8 +134,7 @@ void ShowWarning( const char *file, int line, const char *message ); // don't pu
/* Use CStdString: */
#include "StdString.h"
typedef const CString& CCStringRef;
using namespace StdString;
/* Include this here to make sure our assertion handler is always
* used. (This file is a dependency of most everything anyway,