https://blog.csdn.net/tttt418zh-cnhttps://blog.csdn.net/https://blog.csdn.net/tttt418/article/details/6122630https://blog.csdn.net/tttt418/article/details/6122630tttt418Fri, 07 Jan 2011 14:52:00 +0800int main(int argc, char* argv[])
{
    FILE * stream;
    if( (stream=fopen("F://1.txt","w+")) !=NULL )
    {
        printf("fp1=%X/n", stream);
        testFile( stream );
    }
    return 0;
}
//dl]]>https://blog.csdn.net/tttt418/article/details/6122126https://blog.csdn.net/tttt418/article/details/6122126tttt418Fri, 07 Jan 2011 11:21:00 +0800抽象出问题是这样的：
 
class DLL_API1 A
{
func()
{
vector vec;
B b;
b.func(vec);
 
return TRUE;
}
}
 
其中B是另一个导出类，定义如下
class DLL_API2 B
{
private:
vector m_vec;
publi]]>https://blog.csdn.net/tttt418/article/details/6113870https://blog.csdn.net/tttt418/article/details/6113870tttt418Mon, 03 Jan 2011 16:52:00 +0800

 1987年，Jim Gray和Gianfranco Putzolu推出了著名的5分钟法则[Gray 1987]，他们通过内存，硬盘的性能以及当时的成本，给出了这样的公式：BreakEvenIntervalinSeconds =
(PagesPerMBofRAM /AccessesPerSecondPerDisk) × (PricePerDiskDrive /PricePerMBofRAM)。并由该公式得到了5分钟左右的近似值，因此做出这样的判断，如果一个数据的]]>https://blog.csdn.net/tttt418/article/details/6113860https://blog.csdn.net/tttt418/article/details/6113860tttt418Mon, 03 Jan 2011 16:47:00 +0800https://blog.csdn.net/tttt418/article/details/6017868https://blog.csdn.net/tttt418/article/details/6017868tttt418Thu, 18 Nov 2010 10:45:00 +0800https://blog.csdn.net/tttt418/article/details/6016633https://blog.csdn.net/tttt418/article/details/6016633tttt418Wed, 17 Nov 2010 22:57:00 +0800
 CString orig("Hello, World!");

    // Convert to a char*
    const size_t newsize = 100;
    char nstring[newsize];
    strcpy(nstring, orig);

另外的方法如下：
方法一: 
char *p; 
CString str="hello"; https://blog.csdn.net/tttt418/article/details/6016456https://blog.csdn.net/tttt418/article/details/6016456tttt418Wed, 17 Nov 2010 22:08:00 +0800SetCheck(TRUE);//选上((CButton *)GetDlgItem(IDC_RADIO1))->SetCheck(FALSE);//不选上((CButton *)GetDlgIt]]>https://blog.csdn.net/tttt418/article/details/6014990https://blog.csdn.net/tttt418/article/details/6014990tttt418Wed, 17 Nov 2010 15:31:00 +0800https://blog.csdn.net/tttt418/article/details/6014974https://blog.csdn.net/tttt418/article/details/6014974tttt418Wed, 17 Nov 2010 15:26:00 +0800https://blog.csdn.net/tttt418/article/details/6013858https://blog.csdn.net/tttt418/article/details/6013858tttt418Wed, 17 Nov 2010 08:51:00 +0800https://blog.csdn.net/tttt418/article/details/6009729https://blog.csdn.net/tttt418/article/details/6009729tttt418Mon, 15 Nov 2010 11:48:00 +0800关于基类和派生类的构造函数这篇文章写的很清楚，转载过来：
 

1. 顺序
      当创建一个派生类的对象时，系统首先自动创建一个基类对象，也就是说，在调用派生类构造函数创建派生类对象之前，系统首先调用基类的构造函数创建基类对象。当派生类对象生命期结束时，首先调用派生类的析构函数，然后调用基类的析构函数。简而言之，就是说，构造函数：基类->派生类。析构函数：派生类->基类。
这个我们完全可以通过一个小程序来说明：//通过输出就可以看出在创建派]]>https://blog.csdn.net/tttt418/article/details/6005934https://blog.csdn.net/tttt418/article/details/6005934tttt418Fri, 12 Nov 2010 21:26:00 +0800https://blog.csdn.net/tttt418/article/details/5966179https://blog.csdn.net/tttt418/article/details/5966179tttt418Tue, 26 Oct 2010 11:02:00 +0800https://blog.csdn.net/tttt418/article/details/5953415https://blog.csdn.net/tttt418/article/details/5953415tttt418Wed, 20 Oct 2010 10:27:00 +0800第一：private, public, protected 访问标号的访问范围。private：只能由1.该类中的函数、2.其友元函数访问。不能被任何其他访问，该类的对象也不能访问。
protected：可以被1.该类中的函数、2.子类的函数、以及3.其友元函数访问。但不能被该类的对象访问。
public：可以被1.该类中的函数、2.子类的函数、3.其友元函数访问，也可以由4.该类的对象访问。 注：友元函数包括3种：设为友元的普通的非成员函数；设为友元的其他类的成员函数；设为]]>https://blog.csdn.net/tttt418/article/details/5150901https://blog.csdn.net/tttt418/article/details/5150901tttt418Thu, 07 Jan 2010 15:21:00 +0800https://blog.csdn.net/tttt418/article/details/5128582https://blog.csdn.net/tttt418/article/details/5128582tttt418Mon, 04 Jan 2010 12:10:00 +0800https://blog.csdn.net/tttt418/article/details/5128531https://blog.csdn.net/tttt418/article/details/5128531tttt418Mon, 04 Jan 2010 11:56:00 +0800https://blog.csdn.net/tttt418/article/details/4559820https://blog.csdn.net/tttt418/article/details/4559820tttt418Wed, 16 Sep 2009 18:03:00 +0800https://blog.csdn.net/tttt418/article/details/4474953https://blog.csdn.net/tttt418/article/details/4474953tttt418Sun, 23 Aug 2009 13:24:00 +0800https://blog.csdn.net/tttt418/article/details/4473161https://blog.csdn.net/tttt418/article/details/4473161tttt418Sat, 22 Aug 2009 17:42:00 +0800