摘要: Though the changes in Visual Studio 2005 represent a major improvement over non-compliant hacks that have been in use since the mid-1990s, fear of breaking existing C++ apps has led many project managers to avoid upgrading. This checklist helps you to locate and repair incompliant code so you can upgrade your apps--without breaking them.
閱讀全文
摘要: C++ Debugging 技術(shù)!
閱讀全文
摘要: 寫xml中的問(wèn)題,大家來(lái)共同討論討論!
閱讀全文
摘要: CPPUnit is a unit testing framework for C++, with which you can improve your systems' quality.
閱讀全文
摘要: Managed, Unmanaged, Native: What Kind of Code Is This?
閱讀全文
摘要: 歸納起來(lái),泛型比非泛型具有下面兩個(gè)優(yōu)點(diǎn):
1、 更加安全
在非泛型編程中,雖然所有的東西都可以作為Object傳遞,但是在傳遞的過(guò)程中免不了要進(jìn)行類型轉(zhuǎn)換。而類型轉(zhuǎn)換在運(yùn)行時(shí)是不安全的。使用泛型編程將可以減少不必要的類型轉(zhuǎn)換,從而提高安全性。
2、 效率更高
在非泛型編程中,將簡(jiǎn)單類型作為Object傳遞時(shí)會(huì)引起B(yǎng)oxing和Unboxing操作,這兩個(gè)過(guò)程都是具有很大開銷的。使用泛型編程就不必進(jìn)行Boxing和Unboxing操作了。
.NET泛型具有很好的二進(jìn)制重用性。這一點(diǎn)得益于.NET將泛型內(nèi)建在CLR之中。C++泛型和評(píng)估中Java泛型所依靠的是它們各自的編譯器所提供的特性,編譯器在編譯泛型代碼時(shí)將確切的類型展開,這就難免會(huì)出現(xiàn)代碼膨脹的問(wèn)題。而.NET的泛型代碼是在運(yùn)行時(shí)由JIT即時(shí)編譯的,這樣CLR就可以為不同類型重用大部分的即時(shí)編譯代碼了。
閱讀全文