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

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

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 魏尚堂 閱讀(156) | 評論 (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 魏尚堂 閱讀(157) | 評論 (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 魏尚堂 閱讀(221) | 評論 (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 魏尚堂 閱讀(158) | 評論 (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 魏尚堂 閱讀(230) | 評論 (0)編輯 收藏

2013年1月24日

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

// 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 魏尚堂 閱讀(681) | 評論 (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, 編譯器匹配方法時非模板函數(shù)優(yōu)先模板函數(shù)
2, 友元函數(shù)模板必須提前聲明

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

2013年1月17日

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

posted @ 2013-01-17 14:01 魏尚堂 閱讀(162) | 評論 (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 魏尚堂 閱讀(150) | 評論 (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>
            狠色狠色综合久久| 国产精品日韩精品欧美精品| 激情综合久久| 麻豆成人91精品二区三区| 久久精品国产免费看久久精品| 欧美日韩国产综合视频在线观看中文| 国产精品揄拍一区二区| 久久精品国语| 欧美福利视频在线| 亚洲免费在线观看| 久久精品免费观看| 99国产麻豆精品| 亚洲愉拍自拍另类高清精品| 国产在线成人| 91久久夜色精品国产九色| 欧美日韩精品系列| 久久av一区二区三区漫画| 久久久久一区二区三区| 中日韩美女免费视频网址在线观看 | 亚洲精品免费在线播放| 亚洲精品一区中文| 国产一区二区毛片| 亚洲黄一区二区三区| 国产女主播一区二区三区| 亚洲国产精品尤物yw在线观看| 欧美日韩麻豆| 欧美xx视频| 国产精品主播| 亚洲精品视频一区| 亚洲福利av| 午夜视频一区二区| 亚洲一线二线三线久久久| 久久久久久9| 欧美一区二区三区视频在线| 欧美久久婷婷综合色| 久久在线免费| 国产精品影片在线观看| 亚洲精品国产精品国自产观看浪潮| 国产精品色午夜在线观看| 亚洲国产精品尤物yw在线观看 | 久久精品30| 小黄鸭视频精品导航| 欧美日韩国产麻豆| 亚洲电影免费观看高清完整版在线| 国产精品视屏| 一区二区三区高清在线| 日韩亚洲欧美在线观看| 久久久久久网| 久久亚洲精品网站| 国产日韩欧美91| 亚洲免费在线观看| 亚洲欧美日韩国产综合精品二区| 久久久久久亚洲精品不卡4k岛国| 亚洲专区在线视频| 欧美视频三区在线播放| 亚洲精品久久7777| 99xxxx成人网| 欧美日韩国产一区二区| 亚洲欧洲日夜超级视频| 日韩视频在线一区二区三区| 欧美激情国产精品| 最新国产成人在线观看| 一本久久综合亚洲鲁鲁| 欧美精品一区二区三区蜜臀| 亚洲欧洲三级电影| 亚洲一二三区视频在线观看| 欧美视频一区二| 亚洲线精品一区二区三区八戒| 99热免费精品| 欧美新色视频| 亚洲一区免费| 久久精品一区二区三区中文字幕| 国产精品久久久久久影视| 亚洲午夜久久久久久久久电影网| 亚洲在线观看免费视频| 国产精品久久一区主播| 小处雏高清一区二区三区| 久久久国产精品一区二区三区| 国产精品自拍在线| 久久久久高清| 亚洲精品影视在线观看| 亚洲男人的天堂在线| 国内偷自视频区视频综合| 久久综合一区二区| 99精品免费视频| 欧美一级日韩一级| 亚洲国产精品成人| 欧美日韩亚洲另类| 欧美在线免费一级片| 亚洲国产欧美日韩| 亚洲专区欧美专区| 影音先锋日韩资源| 欧美日韩亚洲在线| 久久精品国产69国产精品亚洲| 免费av成人在线| 亚洲亚洲精品在线观看| 激情一区二区| 国产精品久久久久aaaa九色| 久久精品国产综合| 夜色激情一区二区| 欧美+亚洲+精品+三区| 亚洲综合日韩| 亚洲欧洲综合另类| 国产欧美日韩视频一区二区三区 | 欧美日韩高清一区| 欧美在线视频a| 一本久久a久久免费精品不卡| 欧美一区二区日韩| 日韩一级不卡| 激情综合中文娱乐网| 国产精品盗摄久久久| 狂野欧美一区| 久久国产精品一区二区| 一区二区免费看| 亚洲韩国日本中文字幕| 久久久久久久波多野高潮日日 | 欧美视频一区二| 欧美1区视频| 久久午夜激情| 日韩一级成人av| 黄色在线一区| 国产一区二区剧情av在线| 国产精品a久久久久久| 欧美精品综合| 欧美高清视频在线观看| 久久蜜臀精品av| 欧美中日韩免费视频| 午夜免费久久久久| 亚洲永久免费精品| 中文国产成人精品| 一区二区三区视频在线播放| 亚洲激情女人| 亚洲精品乱码久久久久久黑人| 久久免费精品日本久久中文字幕| 亚洲午夜一区| 亚洲一级影院| 亚洲综合色视频| 亚洲一区二区在线观看视频| 亚洲美女视频网| 日韩午夜av电影| 中文高清一区| 亚洲女人天堂成人av在线| 亚洲一区二区三区影院| 亚洲中无吗在线| 香港久久久电影| 久久久久久999| 欧美.www| 亚洲日韩中文字幕在线播放| 日韩网站在线观看| 在线一区二区三区四区| 亚洲在线免费观看| 久久成人一区| 欧美成人官网二区| 欧美视频日韩| 国产欧美一区二区精品忘忧草 | 欧美激情视频在线播放| 欧美精品在线播放| 国产精品久久久久一区二区三区共| 欧美视频在线观看视频极品| 国产精品久久久久91| 国内外成人免费激情在线视频网站| 国产主播精品| 日韩视频一区二区三区| 亚洲欧美bt| 另类酷文…触手系列精品集v1小说| 狂野欧美一区| 亚洲啪啪91| 午夜一区不卡| 欧美激情亚洲自拍| 国产精品一区视频| 亚洲国产精品www| 午夜精品福利一区二区蜜股av| 欧美一级二区| 亚洲国产天堂网精品网站| 一区二区三区四区国产| 久久国产精品高清| 欧美午夜精品伦理| 欲色影视综合吧| 亚洲欧美日本另类| 亚洲成人资源| 欧美一级一区| 欧美调教视频| 亚洲激情六月丁香| 欧美在线亚洲一区| 亚洲久久成人| 老司机aⅴ在线精品导航| 国产精品成人观看视频免费| 亚洲高清免费视频| 欧美一区二区三区在线看| 亚洲国产一区二区三区高清| 欧美一级成年大片在线观看| 欧美日韩一卡二卡| 亚洲国产精品久久久| 久久爱www| 在线一区亚洲| 欧美日韩国产精品一区| 亚洲黄色成人久久久| 久久在线免费| 欧美在线精品免播放器视频| 国产精品免费小视频|