法爾斯文翻譯object),來代替 C 的函式指標的技術。
來形容它。
                                                                               
                                                                               
也就是 object-based 的根本,讓程式設計師可以更進一步以嚴謹、平安,天然、
每一種編程技術的支援,都到達最完整的水平。正因為它完整,才能儘可能切近前
                                                                               
                                                                               
                                                                               
  C++ 用以具現泛型編程設計模式的方式,是引入樣版(template)及其他互相
  sum += i^100;
                                                                               
工致的編排組織起來翻譯
                                                                               
                                                                               
                                                                               
  甚至,若是你喜歡 BASIC 的次方(^)符號表式法,你可以在 C++ 中本身設計
代 C 的巨集,引入 const、mutable、new、delete 等關鍵字,增強物件和記憶體管
                                                                               
  在注釋之前,先說一點,C 和 C++ 的分歧的地方就在於,以上所列 C++ 的四
                                                                               
或,常聽到有人說,C++ 是 C 的超調集(或 C 是 C++ 的子集),或者,C++
  最後,generic paradigm,泛型編程翻譯這是相當晚近才興起的程式設計的思惟
                                                                               
  b = "458349057395730974539451048634826832629683342310298457";
   總之,以上所接洽的每項特征,都使得 C++ 的程式設計,在底子上就和 C 說話
理念付諸實現翻譯
, C 說話中所有物件(變數、佈局)的宣佈都要放在最前面,在 C++ 則沒有
                                                                               
  2. object-based paradigm  
  若是翻譯公司熟悉 C,但不熟習 C++,翻譯公司必然會說:「這怎麼可能?????」但這
                                                                               
                                                                               
,就不多討論了翻譯不外有一點可以提出來:只有少數的語言支援完全的多重擔當,
面提過的「利用者不需要為他沒有用到的功能付出效率的價格」,如許的抱負。
進修程式設計的思惟方式);但,要體味 C++ 的精華,先認識 C 的特征和氣勢派頭
                                                                               
                                                                               
,就是:「利用者不該為他沒有效到的功能支付效力的價值」。這句話直接的
                                                                               
  c %= d;
解決,只能好自為之。但在 C++ 上,假如種別設計夠嚴謹,編譯/聯絡器平常可以
                                                                               
和效力的精力,所透露的潛力被一致看好,泛型編程理念的很早就被引入了 C++,
                                                                               
                                                                               
                                                                               
                                                                               
  Essential COM 的作者 Don Box 在書中提到:C++ 此中一個主要的理念,就
                                                                               
  事實上,C++ 所有分歧於 C 的功能,都是為了達成上述的更嚴謹、平安、一致
  4. generic paradigm
                                                                               
一點只是想申明,C++ 不但支援四種首要的編程手藝,更主要的環節在於:C++ 對
而明白,例如你可以「等閑」寫出像 BigInt(超大整數)、VarLenInt(變動長度的
                                                                               
                                                                               
面再诠釋)
                                                                               
幫你解決很多小麻煩。此外,如果你的 BigInt 種別設計允當,它執行時的效力,
                                                                                                                    
擴充性更高。
                                                                               
                                                                               
一個,然後就能夠簡單的計較像 1^100 + 2^100 + ... + 100^100 = ? 這類問題:
                                                                               
曾示意,他認為 Java 遲早也會加入類似 C++ 的 template 的機制,這是任何一個
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
就更優美、輕易浏覽、理解,一致性高,就不容易犯錯,方便維護。總之,封裝機制對
                                                                               
們行將評論辯論的主題,C++ 就是靠著別的三項(C 說話其實不支援的)編程手藝,將此
                                                                               
                                                                               
整數)、Matrix(矩陣)、DateTime ……等等的種別。語法表達自然、明白,程式
一致的體式格局,模塑抽象的思惟世界翻譯這部份在觀念和手藝上都有相當水平的複雜性
                                                                               
C 及 C++ 是今朝最受歡迎的說話之「二」翻譯常人常常感覺二者差不多,
、明白、彈性、擴充性、效力……等等的方針。例如以 const 和 inline 儘可能取
                                                                               
邁向成熟而完整的說話天然的趨向翻譯
                                                                               
例如不當心把 BigInt 和浮點數混用;像這類的問題,在 C 上平日都沒有門徑完全
 BigInt sum = 0;
不會比同樣功能的 C 程式碼最好化後要差翻譯
                                                                               
                                                                               
(包括以位元)操作記憶體的邃密精美性。
                                                                               
引申意義則是:「C++ 兼具了效力與彈性」翻譯舉個例子,華頓翻譯公司們都知道,在之前
 for (BigInt i=1; i<=100; ++i)
 a = "-3298347290354325472309573874327432094739742071561";
這二者便是幾年前一般所謂的「物件導向」編程模式(現在之所以有所辨別,是因
                                                                               
是讓利用者可以自訂型別,而且在處置自訂型別時,和操作內建型別一樣自然、便
                                                                               
                                                                               
                                                                               
體組件抱負最主要的第一步。
結(dynamic binding)的機制翻譯
                                                                               
  c = -a/4 + b * 2;
                                                                               
                                                                               
                                                                               
你可以嚴厲地制定型別安全(type safe)的規格,儘早地讓毛病的操作行為曝露,
  概略地說,C 自己十分精簡,保存字少少,語法簡練、設計氣勢派頭偏向切確、
                                                                               
                                                                               
篇答複書記中曾接頭過,這個說法應當只是指說話自己,而不是指直接透過 C++
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
一致明白的語法表達、加倍具有彈性和擴充性,且更有用率的函式物件(function
                                                                               
太意外了。
模式。很幸運地,在 C++ 還不是很完備時,由於全部說話在各方面貫串了兼具彈性
之卻步)的其中一個原因就在於:C 具有指標的設計,可以在最大限度的範圍內
                                                                               
種編程思維,C 只提拱了第一種,也就是我們常聽到的「法式(功能)導向」模
合營的機制(如 RTTI,動態型別辨識),和在泛型編程的根本上,合適了嚴酷的
                                                                               
                                                                               
                                                                               
                                                                               
  固然,完全的多重繼續增加了語法的複雜度,使用上不見得是優點。但提出這
,不敷完全。事實上,C 和 C++ 的差距非常大。
所謂周全是指:編譯/聯絡器提供更嚴謹、更平安的查抄,語法表達更一致明白、
靈巧翻譯它同時具有高階語言流程節制與資料處置懲罰的便利性,和低階語言直接
                                                                               
                                               像這樣的語法表達,在沒有或對 object-based 編程技術支援不敷完備的說話
                                                                               
某些物件根本用不到,卻必需在函式每次履行的時候去設置裝備擺設記憶體。
                                                                               
                                                                               
  言歸正傳,所謂 object-based paradigm 和 object-oreinted paradigm ,
                                                                               
為程式設計的思惟觀念更進步了,所以又有更細密的區隔)。概略地說,前者是指
  C++ 承續了 C,固然也支援函式指標,但 C++ 程式的風格,其實不激勸利用指
  舉例而言,在 C++ 中,你可以寫一個支援四則運算的超大整數 BigInt 的種別,
                                                                               
                                                                               
編程。透過 C++ 種別(class)的封裝機制,你可以讓程式說話表達地更自然、一致
client(利用這些類別的人)而言,是極為便當而不可或缺的,幾近可以說是邁向軟
式--把功能切割成恰當的小模組,在 C 語言中就是一個一個小函式,再按需求
                                                                               
 3. object-oriented paradigm
又相輔相成的程式設計的思維模式:(因為沒有準確的字面譯詞,先寫英文,後
                                                                               
                                                                               
                                                                        ,照舊很有幫助的翻譯
沒有提供多重繼承,而 Java 也只支援有限型式的多重繼續。
                                                                               
                                                                               
                                                                               
                                                                               
  int d = 4;
經常去處理複雜、過於低階的陣列、指標、位元等等運算(固然有必要時仍是該這麼
                                                                               
是事實。並且,事實不只如斯,可以說,幾近在每一個處所,C++ 都全面超出了 C(
                                                                               
斷成長進化的過程當中,直至目前為止,已綜合歸納出,並且實現了四種分歧,而
                                                                               
                                                                               
  其次,繼承和動態繫結,也就是 object-oriented 編程手藝,建築在封裝,
而目前,泛型編程的手藝在 C++ 上的實現應當也是最成熟的。B.S.(C++的發現人)
                                                                               
                                                                               
                                                                               
效率要求的,可謂最「標準」的函式庫 STL(Standard Template Library) 。有了
                                                                               
的氣勢派頭完全分歧。在大都人的心目中,C 是簡練、乖巧、短小精桿的,而 C++,固然
                                                                               
                                                                               
                                                                               
不克不及說沒出缺點(沒出缺點就暗示沒有進步空間了),但我還是只能用獨一的「偉大」
                                                                               
                                                                               
了生產力。(當然條件是要學得會)
                                                                               
  那麼 C++ 到底有何分歧呢?用一句最簡單的話說,貫穿 C++ 的整個理念
                                                                               
太多太多,每一項,都是為了讓程式設計更嚴謹、明白、語法更天然、簡潔、一致、
                                                                               
,自由矯捷地操控記憶體翻譯而在嚴謹的程序導向編程思惟的年代,像 C 這類支援
                                                                               
                                                                               
做),而可以放心的利用兼具效能、移植性和擴充性的 STL 組件和演算法,大大晉升
利。以上這段話或許可以當作詮釋「封裝」的註腳,這也就是所謂的 object-based
                                                                               
指向函式的指標這類禁斷手藝的說話,會在眾語言百家爭鳴下脫穎而出,也就不
  固然,連 C++ 的發現人都說,可以不用學 C,直接學 C++(敝人在之前一
 BigInt a翻譯社 b, c;
而 C++ 恰是其中之一;其他如 Objective C, Object Pascal, Smalltalk 等,並
                                                                               
                                                                               
  1. procedural-based paradigm
                                                                               
封裝(encapsulation)的編程模式;而後者涵蓋了擔當(inheritance)及動態繫
                                                                               
                                                                               
                                                                               
加倍具有彈性和擴充性,同時不損失、乃至提升效力)(獨一的瑕玷,呃……,大
而言,都是不行能實現的翻譯並且,透過 C++ 封裝機制和其他如異常處置懲罰的支援,
                                                                               
STL,程式設計師不用再每次本身寫 tree、list、stack、queue ...等等,也不需要
概就是,它艱巨的水平,也周全超出了 C)(世界沒有白吃的午餐)。翻譯公司應當會想
向函式的指標。在 C++ 中,供給了一種更嚴謹、具備型別平安(type safe)、更
                                                                               
                                                                               
                                                              以上只是個很小的例子,總之,C++ 為了達成兼容效力和彈性的理念,在不
                                                                               
  必須分外提到一點,C 之所以受很多程式設計師青睞(也同時令另外一些人望
                                                                               
                                                                               
                                                                               
                                                                               
                                                                               
就是支援物件導向的 C。固然,不克不及說這些講法是錯的;是的,這些沒錯,只是
問:「真的嗎?假如是真的,C++ 究竟是怎麼做到的?」沒錯,並且這就是之前我
理、引入 exception 異常處理的機制、引入 namespace 定名空間的機制……等等,
                                                                               
這個限制。顯然,C++ 的體例比較公道,因為強制把宣佈放在最前面,極可能
                                                                               
                                                                               
                                                                               
                                                                               
                                                                            讓它在使用上與內建型別毫無別離:


本文引用自: http://blog.xuite.net/edison901/documents/3753230-C+%E5%92%8C+C%2B%2B+%E7%9A%84%E5%B7%AE%E5%88%A5+--有關各國語文翻譯公證的問題歡迎諮詢華頓翻譯公司02-77260932

arrow
arrow
    文章標籤
    翻譯社
    全站熱搜

    julianr7154ln 發表在 痞客邦 留言(0) 人氣()