青青草原综合久久大伊人导航_色综合久久天天综合_日日噜噜夜夜狠狠久久丁香五月_热久久这里只有精品

posts - 9, comments - 0, trackbacks - 0, articles - 0
  C++博客 :: 首頁 :: 新隨筆 :: 聯系 :: 聚合  :: 管理

2013年5月17日

  • Make sure operator= is well-behaved when an object is assigned to itself. Techniques include comparing addresses of source and target objects, careful statement ordering, and copy-and-swap.

  • Make sure that any function operating on more than one object behaves correctly if two or more of the objects are the same.

posted @ 2013-05-17 15:00 魏尚堂 閱讀(162) | 評論 (0)編輯 收藏

This is only a convention; code that doesn't follow it will compile. However, the convention is followed by all the built-in types as well as by all the types in  the standard library (e.g., string, vector, complex, tr1::shared_ptr, etc.). Unless you have a good reason for doing things differently, don't.

posted @ 2013-05-17 12:06 魏尚堂 閱讀(165) | 評論 (0)編輯 收藏

base class constructors execute before derived class constructors, derived class data members have not been initialized when base class constructors run. If virtual functions called during base class construction went down to derived classes, the derived class functions would almost certainly refer to local data members, but those data members would not yet have been initialized.Calling down to parts of an object that have not yet been initialized is inherently dangerous, so C++ gives you no way to do it.

#include <iostream>
#include <string>
#include <cstdlib>
void print(std::string str){std::cout << str<< std::endl;}
class Transaction {
    public:
        Transaction()
        {
            print("Transaction Constructor");
            logTransaction();
        }
        virtual void logTransaction() const // =0;
        {
            print("Transaction Log");
        }
};
class BuyTransaction: public Transaction
{
    public:
        BuyTransaction(){   print("BuyTransaction Constructor");}
        virtual void logTransaction() const
        {
            print("BuyTransaction Log");
        }
};
int main()
{
    BuyTransaction dbc;
    //dbc.logTransaction();
}
pure virtual functions cannot link.
[shangtang@BTSOM-1 study]$ g++ TestT.cpp
TestT.cpp: In constructor 'Transaction::Transaction()':
TestT.cpp:14: warning: abstract virtual 'virtual void Transaction::logTransaction() const' called from constructor
/tmp/ccXFzaHv.o: In function `Transaction::Transaction()':
TestT.cpp:(.text._ZN11TransactionC2Ev[Transaction::Transaction()]+0x7f): undefined reference to `Transaction::logTransaction() const'
collect2: ld returned 1 exit status
virtual function can compile, run, but with surprise result
[shangtang@BTSOM-1 study]$ ./a.out
Transaction Constructor
Transaction Log
BuyTransaction Constructor

The only way to avoid this problem is to make sure that none of your constructors or destructors call virtual functions on the object being created or destroyed and that all the functions they call obey the same constraint.

posted @ 2013-05-17 11:27 魏尚堂 閱讀(230) | 評論 (0)編輯 收藏

Depending on the precise conditions under which such pairs of simultaneously active exceptions arise, program execution either terminates or yields undefined behavior. In this example, it yields undefined behavior.
C++ does not like destructors that emit exceptions!
#include <iostream>
#include <vector>
struct Exception
{
    Exception(){std::cout << "Exception Constructor" << std::endl;}
    ~Exception(){std::cout << "Exception Destructor" << std::endl;}
};
class Widget {
public:
  ~Widget() {std::cout << "Widget Destructor" << std::endl; throw Exception();
  }        //this might emit an exception
  void print(){std::cout << "print" << std::endl;}
};
                
void doSomething();
int main()
{
    doSomething();
}
void doSomething()
{
  std::vector<Widget> v;
  v.push_back(Widget());
  v.push_back(Widget());
  v.push_back(Widget());
  v.push_back(Widget());
  std::vector<Widget>::iterator it = v.begin();
  while(it != v.end())
  {
    std::cout << "end" << std::endl;
    (*it).print();
    it++;
  }
}
complie with g++
[shangtang@BTSOM-1 study]$ ./a.out
Widget Destructor
Exception Constructor
terminate called after throwing an instance of 'Exception'
Aborted (core dumped)
There are two primary ways to avoid the trouble.

   1, Terminate the program if catch a exception, typically by calling std::abort (cstdlib)
  2, 
Swallow the exception if catch a exception, print a log

posted @ 2013-05-17 10:56 魏尚堂 閱讀(164) | 評論 (0)編輯 收藏

2013年5月13日

1, Declare destructors virtual in polymorphic base classes
why ? because C++ specifies that when a derived class object is deleted through a pointer to a base class with a non-virtual destructor, results are undefined.What typically happens at runtime is that the derived part of the object is never destroyed

2, if a class is not intended to be a base class, making the destructor virtual is usually a bad idea. 
why?  if a class have virtual functions, it has extra overhead(vptr).

3, In fact, many people summarize the situation this way: declare a virtual destructor in a class if and only if that class contains at least one virtual function

4,Sometimes, however, you have a class that you'd like to be abstract, but you don't have any pure virtual functions.
solution: declare pure virtual destructor.
There is one twist, however you must provide a definition for the pure virtual destructor, or linker will complain.

5, Not all base classes are designed to be used polymorphically. Neither the standard string type, for example, nor the STL container typesare designed to be base classes at all, much less polymorphic ones.


 
 

posted @ 2013-05-13 14:45 魏尚堂 閱讀(238) | 評論 (0)編輯 收藏

2013年1月24日

thinking in c++ 有下面的例子,不太理解為什么這個宏中的條件表達式在編譯時就執行了,在此作個記號

// A simple, compile-time assertion facility
#define STATIC_ASSERT(x) \
   do { typedef int a[(x) ? 1 : -1]; } while(0)

int main()
{
   STATIC_ASSERT(sizeof(int) <= sizeof(long));  // Passes
   STATIC_ASSERT(sizeof(double) <= sizeof(int)); // Fails 
   return 0;
}

posted @ 2013-01-24 10:26 魏尚堂 閱讀(688) | 評論 (0)編輯 收藏

2013年1月21日

template <typename T> class dataList
{
   public:
      friend ostream& operator<<(ostream& outStream, const dataList <T> &outList);
}
template <typename T> ostream& operator<<(ostream& outStream, const dataList <T> &outList)
{
   //....
   return outStream;
}
int main(int argc, char* argv[])
{
   dataList <int> testList;
   cout << testList;
}
這個程序員是鏈接不過,
錯誤信息:
 warning: friend declaration âstd::ostream& operator<<(std::ostream&, const dataList<T>&)â declares a non-template function
 note: (if this is not what you intended, make sure the function template has already been declared and add <> after the function name here)
/tmp/cc9DSuka.o: In function `main':
undefined reference to `operator<<(std::basic_ostream<char, std::char_traits<char> >&, dataList<int> const&)'
collect2: ld returned 1 exit status
錯誤原因解釋

The problem is that the compiler is not trying to use the templated operator<< you provided, but rather a non-templated version.

When you declare a friend inside a class you are injecting the declaration of that function in the enclosing scope. The following code has the effect of declaring (and not defining) a free function that takes a non_template_test argument by constant reference:

class non_template_test { friend void f( non_template_test const & ); }; // declares here: // void f( non_template_test const & );

The same happens with template classes, even if in this case it is a little less intuitive. When you declare (and not define) a friend function within the template class body, you are declaring a free function with that exact arguments. Note that you are declaring a function, not a template function:

template<typename T> class template_test { friend void f( template_test<T> const & t ); }; // for each instantiating type T (int, double...) declares: // void f( template_test<int> const & ); // void f( template_test<double> const & );  int main() {     template_test<int> t1;     template_test<double> t2; }

Those free functions are declared but not defined. The tricky part here is that those free functions are not a template, but regular free functions being declared. When you add the template function into the mix you get:

template<typename T> class template_test { friend void f( template_test<T> const & ); }; // when instantiated with int, implicitly declares: // void f( template_test<int> const & );  template <typename T> void f( template_test<T> const & x ) {} // 1  int main() {    template_test<int> t1;    f( t1 ); }

When the compiler hits the main function it instantiates the template template_test with type intand that declares the free function void f( template_test<int> const & ) that is not templated. When it finds the call f( t1 ) there are two f symbols that match: the non-template f( template_test<int> const & ) declared (and not defined) when template_test was instantiated and the templated version that is both declared and defined at 1. The non-templated version takes precedence and the compiler matches it.

When the linker tries to resolve the non-templated version of f it cannot find the symbol and it thus fails.

What can we do? There are two different solutions. In the first case we make the compiler provide non-templated functions for each instantiating type. In the second case we declare the templated version as a friend. They are subtly different, but in most cases equivalent.

Having the compiler generate the non-templated functions for us:

template <typename T> class test  { friend void f( test<T> const & ) {} }; // implicitly

This has the effect of creating as many non-templated free functions as needed. When the compiler finds the friend declaration within the template test it not only finds the declaration but also the implementation and adds both to the enclosing scope.

Making the templated version a friend

To make the template a friend we must have it already declared and tell the compiler that the friend we want is actually a template and not a non-templated free function:

template <typename T> class test; // forward declare the template class template <typename T> void f( test<T> const& ); // forward declare the template template <typename T> class test { friend void f<>( test<T> const& ); // declare f<T>( test<T> const &) a friend }; template <typename T> void f( test<T> const & ) {}

In this case, prior to declaring f as a template we must forward declare the template. To declare the ftemplate we must first forward declare the test template. The friend declaration is modified to include the angle brackets that identify that the element we are making a friend is actually a template and not a free function.
引用自 http://stackoverflow.com/questions/1810753/overloading-operator-for-a-templated-class
從上面我可以學到一點:
1, 編譯器匹配方法時非模板函數優先模板函數
2, 友元函數模板必須提前聲明

posted @ 2013-01-21 10:48 魏尚堂 閱讀(612) | 評論 (0)編輯 收藏

2013年1月17日

Linux Shell的通配符與正則表達式 http://blog.csdn.net/chen_dx/article/details/2463495

posted @ 2013-01-17 14:01 魏尚堂 閱讀(166) | 評論 (0)編輯 收藏

2012年11月27日

Perform every resource allocation (e.g., new) in its own code statement which immediately gives the new resource to a manager object (e.g., auto_ptr).

This guideline is easy to understand and remember, it neatly avoids all of the exception safety problems in the original problem, and by mandating the use of manager objects it helps to avoid many other exception safety problems as well. This guideline is a good candidate for inclusion in your team's coding standards

link http://www.gotw.ca/gotw/056.htm

file I/O http://www.zwqxin.com/archives/cpp/use-sstream.html

posted @ 2012-11-27 10:03 魏尚堂 閱讀(155) | 評論 (0)編輯 收藏

青青草原综合久久大伊人导航_色综合久久天天综合_日日噜噜夜夜狠狠久久丁香五月_热久久这里只有精品
  • <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>
            狠狠色丁香婷婷综合| 欧美一级艳片视频免费观看| 一区二区三区鲁丝不卡| 在线播放亚洲一区| 国产一区二区三区在线免费观看| 欧美视频第二页| 欧美日韩一区精品| 国产精品成av人在线视午夜片| 欧美四级剧情无删版影片| 国产精品久久久久91| 国产欧美日韩亚洲| 久久国产精品黑丝| 欧美成人四级电影| 欧美在线免费视频| 久久精品人人做人人爽| 久久午夜视频| 欧美日韩亚洲视频一区| 国产亚洲成人一区| 亚洲欧洲另类| 亚洲欧美日韩视频一区| 久久久蜜臀国产一区二区| 麻豆精品一区二区av白丝在线| 免费在线日韩av| 99国产精品国产精品久久 | 一区二区三区视频在线观看 | 国产日韩欧美91| 在线精品一区二区| 亚洲欧美国产77777| 另类国产ts人妖高潮视频| 亚洲精品极品| 一区二区欧美亚洲| 久久久人成影片一区二区三区| 欧美国产精品专区| 国内精品久久久| 一本一本久久| 美女爽到呻吟久久久久| 99亚洲一区二区| 免费成人av| 国产在线不卡| 亚洲欧美精品一区| 日韩视频在线观看一区二区| 久久精品一区四区| 国产精品人成在线观看免费 | 亚洲一区三区视频在线观看| 男女激情久久| 久久精品欧美日韩| 国产日韩欧美在线看| 亚洲一二区在线| 欧美激情四色| 免费日韩成人| 亚洲激情视频在线| 久热爱精品视频线路一| 欧美亚洲综合网| 国产欧美午夜| 久久久av毛片精品| 久久av红桃一区二区小说| 国产日产欧美一区| 久久国产精品久久久久久| 99热这里只有精品8| 欧美激情自拍| 91久久在线观看| 亚洲激情网站| 欧美理论电影在线观看| 一本一本久久a久久精品综合妖精 一本一本久久a久久精品综合麻豆 | 久久一区二区三区四区| 亚洲视频图片小说| 欧美日韩伦理在线免费| 亚洲精品自在在线观看| 亚洲国产精品免费| 欧美国产亚洲精品久久久8v| 亚洲第一精品福利| 欧美国产综合一区二区| 欧美jjzz| 一区二区三区|亚洲午夜| 99精品视频免费| 国产精品视频免费观看| 久久精品二区三区| 欧美一区二区三区在| 国产自产精品| 欧美成人亚洲成人| 欧美日韩精品一区二区天天拍小说| 99国产精品久久久久老师| 日韩亚洲欧美成人| 国产精品私房写真福利视频| 久久久之久亚州精品露出| 久久中文字幕一区二区三区| 99亚洲伊人久久精品影院红桃| 99国内精品久久| 国产性色一区二区| 欧美成人首页| 国产精品成人一区二区网站软件| 欧美中文字幕久久| 久热综合在线亚洲精品| 亚洲男同1069视频| 久久久夜精品| 亚洲免费在线视频一区 二区| 亚洲欧美伊人| 亚洲在线观看视频| 激情视频一区二区| 亚洲黄色性网站| 国产精品久久久久9999高清 | 亚洲女优在线| 欧美在线高清| 亚洲尤物在线| 久久亚洲免费| 欧美中文在线观看| 欧美日韩免费观看一区三区| 久久精品青青大伊人av| 欧美bbbxxxxx| 久久久精品日韩欧美| 欧美日韩一区不卡| 欧美阿v一级看视频| 国产精品久久久久久久久久妞妞 | 久久天堂国产精品| 亚洲永久免费av| 久久婷婷丁香| 久久国产乱子精品免费女| 亚洲大胆在线| 国产人妖伪娘一区91| 亚洲精品在线免费观看视频| 精品99一区二区| 亚洲欧洲av一区二区| 国产精品99久久久久久久vr| 欧美在线精品免播放器视频| 亚洲午夜精品国产| 欧美国产日本韩| 欧美激情精品久久久久久| 国产婷婷色一区二区三区四区| 欧美午夜欧美| 欧美成人激情在线| 国产日韩欧美在线播放| 中文高清一区| 亚洲在线一区| 欧美日韩午夜剧场| 亚洲啪啪91| 亚洲精品少妇网址| 久久香蕉国产线看观看av| 久久久久免费| 国产欧美日韩一区二区三区在线| 99pao成人国产永久免费视频| 亚洲人屁股眼子交8| 麻豆91精品| 亚洲精品久久久久久久久久久久| 91久久精品国产91久久性色tv | 亚洲欧美日韩中文播放| 欧美黑人在线播放| 亚洲国产裸拍裸体视频在线观看乱了中文| 国产曰批免费观看久久久| 篠田优中文在线播放第一区| 久久精品毛片| 国模 一区 二区 三区| 久久精品一区四区| 免费日韩av| 亚洲国产精品ⅴa在线观看 | 久久久五月天| 免费的成人av| 日韩亚洲欧美综合| 欧美激情第1页| 亚洲精品系列| 午夜精品久久久久| 国产午夜精品全部视频播放| 在线成人欧美| 欧美国产日韩xxxxx| 亚洲精品日韩欧美| 欧美在线免费视屏| 亚洲第一综合天堂另类专| 欧美激情区在线播放| 99国产一区| 老鸭窝毛片一区二区三区 | 午夜精品久久久久久久久久久久| 国产精品日韩精品欧美在线| 欧美一区二区福利在线| 欧美成人午夜激情在线| 亚洲视频自拍偷拍| 国产亚洲欧美日韩美女| 欧美成人一区二区三区在线观看| 亚洲美女福利视频网站| 久久成人精品| av不卡在线观看| 国产真实久久| 欧美三级精品| 亚洲激情网站免费观看| 亚洲在线视频网站| 亚洲电影在线观看| 欧美无乱码久久久免费午夜一区| 亚洲伊人久久综合| 亚洲国产另类久久久精品极度| 亚洲一区国产| 亚洲免费观看高清完整版在线观看| 国产精品va在线播放我和闺蜜| 欧美在线视频免费播放| 亚洲精品久久久久久久久久久久久 | 麻豆精品在线观看| 亚洲欧美成人网| 亚洲东热激情| 久久免费视频网| 亚洲一区二区三区免费视频| 91久久精品一区二区别| 国产一区观看| 国产女人aaa级久久久级|