Garbage collection is nearly everyone s favorite feature of the java platform ; it simplifies development and eliminates entire categories of potential code errors 垃圾收集幾乎是每個(gè)開發(fā)人員都喜愛的一個(gè)java平臺(tái)特性,它簡(jiǎn)化了開發(fā),消除了所有種類的潛在代碼錯(cuò)誤。
Describes the warnings , indicates each warning s level , and indicates potential problems rather than actual coding errors with statements that may not compile as you intend 描述這些警告,指示各個(gè)警告的等級(jí),并指示可能無法按照預(yù)期編譯的語句的潛在問題(而非實(shí)際編碼錯(cuò)誤) 。
For whether the listener is registered before registering it , and throw an exception or log an error if it is , so that evidence of the coding error can be gathered and acted on ,在登記偵聽器之前檢查是否已經(jīng)登記了,如果已經(jīng)登記,就拋出異常(或記錄錯(cuò)誤) ,這樣就可以搜集編碼錯(cuò)誤的證據(jù),并采取行動(dòng)。
One nice touch to pocketc s interaction with the memo pad is that in the instance of a source code error , pocketc gives you the opportunity to jump straight to the error , and highlights it Pocketc與memo pad交互的一個(gè)有益之處是,在出現(xiàn)源代碼錯(cuò)誤的情況中, pocketc提供了直接跳到錯(cuò)誤并突出顯示它的機(jī)會(huì)。
Most coding errors that result in security vulnerabilities occur because developers make invalid assumptions when working with user input or because they do not fully understand the platform for which they are developing 導(dǎo)致安全漏洞的大多數(shù)編碼錯(cuò)誤都是由于開發(fā)人員在處理用戶輸入時(shí)所做的假定不合理,或者是由于他們對(duì)所針對(duì)的平臺(tái)了解不夠充分。