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

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 魏尚堂 閱讀(164) | 評論 (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 魏尚堂 閱讀(168) | 評論 (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 魏尚堂 閱讀(237) | 評論 (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 魏尚堂 閱讀(167) | 評論 (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 魏尚堂 閱讀(240) | 評論 (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 魏尚堂 閱讀(690) | 評論 (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 魏尚堂 閱讀(615) | 評論 (0)編輯 收藏

2013年1月17日

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

posted @ 2013-01-17 14:01 魏尚堂 閱讀(168) | 評論 (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 魏尚堂 閱讀(158) | 評論 (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>
            欧美xart系列高清| 国产精品久久久久久久久免费桃花 | 免费成人小视频| 欧美专区在线| 在线观看成人av电影| 欧美成人免费全部| 欧美日韩精品国产| 欧美一区在线视频| 久久久久九九九| 亚洲另类在线视频| 亚洲性色视频| 黄色日韩在线| 亚洲美女av电影| 国产精品一区二区久久久| 久久精品在线| 欧美激情在线观看| 香蕉视频成人在线观看 | 欧美电影免费观看大全| 女女同性女同一区二区三区91| 99视频热这里只有精品免费| 亚洲香蕉视频| 亚洲高清三级视频| 亚洲天堂网在线观看| 一区视频在线看| 妖精视频成人观看www| 国产在线欧美日韩| 99re6热只有精品免费观看| 国产午夜精品久久久| 亚洲精品在线视频| 国产自产女人91一区在线观看| 亚洲黄色性网站| 国产欧美一区二区三区在线老狼| 亚洲高清一区二区三区| 国产精品视频xxx| 亚洲国产精品久久人人爱蜜臀| 国产精品亚洲视频| 亚洲国内欧美| 黄色亚洲网站| 亚洲欧美成人| 一区二区黄色| 欧美xart系列在线观看| 久久av一区二区三区| 欧美日韩国产一级| 欧美14一18处毛片| 国产在线观看91精品一区| 亚洲人成欧美中文字幕| 影音先锋一区| 久久精品成人| 欧美在线精品一区| 欧美日韩综合精品| 亚洲国产婷婷香蕉久久久久久99| 韩日欧美一区二区| 午夜视频在线观看一区二区| 亚洲午夜小视频| 欧美日本精品| 亚洲精美视频| 日韩午夜电影在线观看| 免费不卡中文字幕视频| 久热这里只精品99re8久| 国产日产欧美a一级在线| 宅男66日本亚洲欧美视频| 一区二区av在线| 欧美激情一区二区三区不卡| 亚洲成人资源网| 亚洲国产高清一区| 美女图片一区二区| 欧美国产一区视频在线观看| 亚洲国产欧美一区二区三区同亚洲| 久久精品国产清高在天天线| 久久久精品视频成人| 国产一二精品视频| 久久精品视频在线播放| 久久亚洲精品网站| 亚洲成人在线免费| 欧美电影美腿模特1979在线看| 亚洲成人资源| 亚洲桃色在线一区| 国产精品日韩欧美综合| 亚洲淫片在线视频| 久久久久国产一区二区三区四区| 国产自产2019最新不卡| 另类成人小视频在线| 91久久精品一区二区三区| av成人国产| 国产精品成人观看视频免费| 午夜在线观看免费一区| 久热爱精品视频线路一| 亚洲精品一区二区三区四区高清| 欧美日韩在线一区| 午夜国产精品视频免费体验区| 久久青草欧美一区二区三区| 亚洲精品乱码久久久久久按摩观| 欧美三级第一页| 久久9热精品视频| 欧美国产精品专区| 亚洲男人的天堂在线观看 | 欧美日韩国产高清视频| 亚洲一区二区黄色| 免费不卡在线观看av| 在线综合欧美| 狠狠色狠狠色综合日日tαg| 欧美国产在线视频| 午夜精品免费视频| 亚洲欧洲一二三| 性久久久久久| 亚洲精品视频在线观看网站| 国产伦精品一区二区三区高清版 | 久久狠狠亚洲综合| 最新成人在线| 久久久久久久久久久久久久一区| 亚洲欧洲精品成人久久奇米网 | 欧美日韩精品免费观看| 久久国产精品第一页| 一区二区欧美在线| 男人的天堂亚洲| 欧美在线播放| 中文欧美字幕免费| 亚洲欧洲综合另类| 韩国av一区二区三区在线观看| 欧美久久电影| 免费成人毛片| 欧美在线观看你懂的| 国产精品99久久久久久www| 亚洲第一伊人| 开心色5月久久精品| 性欧美大战久久久久久久免费观看 | 裸体一区二区| 久久久www| 午夜精品一区二区在线观看 | 欧美激情综合色| 蜜臀va亚洲va欧美va天堂| 亚欧成人精品| 亚洲欧美在线免费| 亚洲视频在线一区| 一区二区三区蜜桃网| 亚洲精品国产无天堂网2021| 亚洲电影免费在线| 亚洲第一成人在线| 伊人久久婷婷色综合98网| 国精品一区二区| 韩国三级电影久久久久久| 国产日韩在线视频| 国产精品日韩一区二区三区| 国产精品久久久久一区二区三区| 欧美色播在线播放| 国产精品久久久久久久久借妻| 欧美三级第一页| 国产精品美女在线观看| 国产精品女人毛片| 国产亚洲视频在线| 国内一区二区三区| 亚洲第一天堂av| 亚洲精品一级| 亚洲图片欧美日产| 欧美一区二区三区免费在线看| 欧美一区二区三区精品电影| 久久精品一区二区三区四区| 裸体歌舞表演一区二区| 欧美成人亚洲成人| 亚洲另类在线一区| 亚洲一区二区三区精品动漫| 亚洲欧美在线高清| 久久人人97超碰精品888 | 一区二区三区四区五区精品视频| 亚洲天堂成人在线观看| 欧美一级视频一区二区| 久久免费视频在线观看| 欧美人体xx| 国产伦精品一区二区三区高清 | 欧美日韩国产成人在线91| 国产精品福利久久久| 国产视频一区三区| 亚洲激情视频在线播放| 亚洲午夜在线观看| 久久久国产精品一区二区三区| 欧美国产日韩视频| 亚洲视频999| 久久在线播放| 国产精品第2页| 亚洲高清网站| 欧美一激情一区二区三区| 欧美成人dvd在线视频| 一区二区三区国产精华| 久久国产免费| 国产精品成人观看视频免费 | 国产一区二区精品久久99| 亚洲人成欧美中文字幕| 欧美一区二区三区视频免费| 亚洲高清在线播放| 午夜精品福利一区二区三区av| 猛干欧美女孩| 国模精品一区二区三区色天香| 亚洲人成在线播放| 久久久欧美精品| 一区二区免费看| 欧美高清在线一区| 激情成人综合| 久久精品91久久香蕉加勒比 | 欧美77777| 午夜精品一区二区三区电影天堂|