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

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>
            欧美金8天国| 久久先锋资源| 久久免费视频在线观看| 午夜日韩av| 午夜免费日韩视频| 久久国产精品亚洲77777| 久久精品一二三区| 久久精品一二三| 欧美黄在线观看| 日韩一级精品| 午夜精品三级视频福利| 欧美一区二区视频观看视频| 亚洲欧美一区二区三区在线| 欧美在线一区二区三区| 久久免费视频一区| 亚洲欧洲精品一区二区| 亚洲高清在线视频| 亚洲一区二区精品| 久久久噜噜噜久久人人看| 欧美电影免费观看高清完整版| 欧美网站在线| 狠狠色丁香婷婷综合影院| 亚洲激情网站| 欧美亚洲在线视频| 欧美电影在线观看| 亚洲一二三区视频在线观看| 久久久亚洲高清| 欧美午夜视频| 亚洲国产日本| 久久久久国产一区二区| 亚洲精选在线观看| 久久激情中文| 欧美性色视频在线| 亚洲国产岛国毛片在线| 亚洲一区二区三区激情| 蜜臀91精品一区二区三区| 亚洲视频一二区| 欧美激情一区二区三区蜜桃视频| 国产偷国产偷精品高清尤物| 一级日韩一区在线观看| 久久综合电影| 午夜久久99| 国产精品美女久久久浪潮软件| 亚洲精品一区在线观看香蕉| 卡通动漫国产精品| 亚洲女女做受ⅹxx高潮| 欧美日韩一区二区三区免费看| 亚洲韩国精品一区| 久久在线观看视频| 先锋资源久久| 国产麻豆精品久久一二三| 在线亚洲一区| 99v久久综合狠狠综合久久| 欧美国产亚洲视频| 亚洲欧洲精品一区二区三区不卡| 久久五月天婷婷| 久久riav二区三区| 韩日精品中文字幕| 久久琪琪电影院| 久久久久久久综合| 一区二区三区在线免费视频| 久久综合亚洲社区| 久久精品国产免费观看| 国内成人精品视频| 久久久五月天| 久久综合影音| 亚洲激情精品| 亚洲乱码国产乱码精品精98午夜| 欧美久久久久久久久| 在线一区视频| 亚洲一本大道在线| 亚洲在线视频观看| 国产乱码精品一区二区三区五月婷| 亚洲欧美日韩精品久久久久| 亚洲尤物影院| 精品999网站| 亚洲国产影院| 欧美日韩在线一区| 性欧美大战久久久久久久免费观看| 亚洲男人的天堂在线观看| 国产亚洲精品久久久| 免费h精品视频在线播放| 久久一区精品| 亚洲亚洲精品在线观看| 亚洲欧美日韩精品一区二区| 在线播放中文字幕一区| 91久久精品国产| 国产欧美va欧美不卡在线| 欧美成人首页| 国产精品麻豆欧美日韩ww | 国产精品日韩欧美| 久久精品久久99精品久久| 噜噜噜在线观看免费视频日韩| 亚洲精品国产精品乱码不99| 中文一区二区在线观看| 一区在线影院| 亚洲乱码国产乱码精品精可以看| 国产网站欧美日韩免费精品在线观看| 欧美高清视频www夜色资源网| 国产精品成人一区二区网站软件| 久热精品在线| 国产精品久久久久久久久久免费看 | 亚洲国产日本| 国产一区美女| 99热这里只有精品8| 伊人色综合久久天天| 日韩亚洲视频| 亚洲电影免费在线观看| 亚洲在线观看视频| 亚洲日本精品国产第一区| 亚洲综合色丁香婷婷六月图片| 亚洲激情偷拍| 久久久精品性| 欧美一区二区三区在线看| 欧美日韩国产精品| 亚洲国产高清一区| 精品成人乱色一区二区| 午夜精品久久久久| 亚洲欧美综合精品久久成人| 欧美.日韩.国产.一区.二区| 久久嫩草精品久久久精品一| 国产乱码精品一区二区三区五月婷 | 久久成人综合视频| 亚洲欧美国产不卡| 欧美大片免费观看在线观看网站推荐| 久久精品在线播放| 国产欧美综合一区二区三区| 一本一本久久a久久精品综合麻豆 一本一本久久a久久精品牛牛影视 | 亚洲人成网站在线观看播放| 久久精品国产99国产精品澳门| 午夜精品久久久久久久蜜桃app | 久久综合国产精品| 国产欧美日韩一区二区三区在线| 99热在线精品观看| 一区二区高清在线| 欧美激情精品久久久久久黑人 | 亚洲欧美日韩高清| 欧美日韩精品一本二本三本| 亚洲日韩欧美视频一区| 亚洲乱码国产乱码精品精天堂 | 国产精品最新自拍| 亚洲专区欧美专区| 欧美一级艳片视频免费观看| 国产精品黄色在线观看| 中国女人久久久| 午夜视频在线观看一区| 国产欧美日韩一区二区三区在线观看 | 亚洲国产精品一区制服丝袜| 久久精视频免费在线久久完整在线看| 久久性天堂网| 亚洲高清一区二区三区| 免费视频一区| 日韩视频一区二区三区在线播放免费观看 | 欧美片第1页综合| 一区二区久久久久久| 午夜在线精品| 狠狠色狠狠色综合人人| 欧美成人精品在线视频| 99视频+国产日韩欧美| 久久精品av麻豆的观看方式| 美女日韩欧美| 91久久精品美女| 午夜欧美精品| 亚洲电影免费观看高清完整版| 欧美久久久久久久久久| 亚洲欧美精品伊人久久| 老鸭窝亚洲一区二区三区| 99热在这里有精品免费| 国产精品女同互慰在线看| 久久九九热免费视频| 亚洲日本成人网| 久久精品国产亚洲一区二区| 亚洲精品影视| 国产三级欧美三级日产三级99| 美女黄毛**国产精品啪啪| 亚洲性夜色噜噜噜7777| 欧美激情小视频| 欧美中文字幕精品| av72成人在线| 一区二区三区在线免费播放| 欧美日韩免费| 久久中文在线| 亚洲欧美另类综合偷拍| 欧美激情精品久久久久久黑人| 午夜在线成人av| av成人免费在线观看| 韩国av一区二区三区| 国产精品国产三级国产普通话蜜臀 | 亚洲天堂av电影| 免费亚洲视频| 欧美中文字幕精品| 亚洲永久免费观看| 亚洲精品一区二区在线| 国产中文一区| 国产精品视频免费观看| 欧美另类极品videosbest最新版本| 久久精品国产99国产精品澳门| 亚洲一区二区三区三| 一本久久综合| 日韩午夜黄色|