编程精粹：编写高质量C语言代码

作者: [美] 马圭尔（StephenA.Maguire）著

出版社: 人民邮电出版社

出版时间: 2009-02

版次: 1

ISBN: 9787115193162

定价: 45.00

装帧: 平装

开本: 16开

纸张: 胶版纸

页数: 256页

字数: 341千字

正文语种: 英语

原版书名: Writing Solid Code

丛书: 图灵程序设计丛书

分类: 计算机与互联网

1 张插图图片

51人买过

　　《编程精粹编写高质量C语言代码(英文版)》给出了多条编程方面的指导，这些指导看似简单，却是作者多年思考及实践的结果，是对其编程经验的总结。书中解决问题的思考过程对于程序开发人员尤显珍贵。
　　软件日趋复杂，编码错误随之而来。要在测试前发现程序的错误，开发出无错误的程序，关键是弄清楚错误为何产生，又是如何产生。 Stephen A.Maguire，世界著名的技术专家和技术作家。曾在微软公司供职多年，领导开发了Mac版的Excel和众多重要的跨平台项目，并多次扮演救火队员的角色，成功拯救那些陷入困境的团队。现为Web开发公司Storm Development的高级副总裁。他的另一部名著Debugging the Develo 1AHYPOTHETICALCOMPILER.
Ifyourcompilercoulddetecteverybuginyourprogram——nomatterthetype——andissueanerrormessage，riddingyourcodeofbugswouldbesimple.Suchomniscientcompilersdontexist，butbyenablingoptionalcompilerwarnings，usingsyntaxandportabilitycheckers，andusingautomatedunittests，youcanincreasethenumberofbugsthataredetectedforyouautomatically.

2ASSERTYOURSELF
Agooddevelopmentstrategyistomaintaintwoversionsofyourprogram：onethatyoushipandonethatyouusetodebugthecode.Byusingdebuggingassertionstatements，youcandetectbugscausedbybadfunctionarguments，accidentaluseofundefinedbehavior，mistakenassumptionsmadebyotherprogrammers，andimpossibleconditionsthatneverthelesssomehowshowup.Debug-onlybackupalgorithmshelpverifyfunctionresultsandthealgorithmsusedinfunctions.

3FORTIFYYOURSUBSYSTEMS
Assertionswaitquietlyuntilbugsshowup.Evenmorepowerfularesubsystemintegritychecksthatactivelyvalidatesubsystemsandalertyoutobugsbeforethebugsaffecttheprogram.TheintegritychecksforthestandardCmemorymanagercandetectdanglingpointers，lostmemoryblocks，andillegaluseofmemorythathasnotbeeninitializedorthathasalreadybeenreleased.Integritycheckscanalsobeusedtoeliminaterarebehavior，whichisresponsibleforuntestedscenarios，andtoforcesubsystembugstobereproduciblesothattheycanbetrackeddownandfixed.

4STEPTHROUGHYOURCODE
Thebestwaytofindbugsistostepthroughallnewcodeinadebugger.Bysteppingthrougheachinstructionwithyourfocusonthedataflow，youcanquicklydetectproblemsinyourexpressionsandalgorithms.Keepingthefocusonthedata，nottheinstructions，givesyouasecond，verydifferent，viewofthecode.Steppingthroughcodetakestime，butnotnearlyasmuchasmostprogrammerswouldexpectitto.

5CANDY-MACHINEINTERFACES
Itsnotenoughthatyourfunctionsbebug-free;functionsmustbeeasytousewithoutintroducingunexpectedbugs.Ifbugratesaretobereduced，eachfunctionneedstohaveonewell-definedpurpose，tohaveexplicitsingle-purposeinputsandoutputs，tobereadableatthepointwhereitiscalled，andideallytoneverreturnanerrorcondition.Functionswiththeseattributesareeasytovalidateusingassertionsanddebugcode，andtheyminimizetheamountoferrorhandlingcodethatmustbewritten.

6RISKYBUSINESS
Giventhenumerousimplementationpossibilitiesforagivenfunction，itshouldcomeasnosurprisethatsomeimplementationswillbemoreerrorpronethanothers.Thekeytowritingrobustfunctionsistoexchangeriskyalgorithmsandlanguageidiomsforalternativesthathaveproventobecomparablyefficientyetmuchsafer.Atoneextremethiscanmeanusingunambiguousdatatypes;attheotheritcanmeantossingoutanentiredesignsimplybecauseitwouldbedifficult，orimpossible，totest.

7TREACHERIESOFTHETRADE
Someprogrammingpracticesaresoriskytheyshouldneverbeused.Mostsuchpracticesareobviouslyrisky，butsomeseemquitesafe，evendesirable，becausetheyfillaneedwithoutapparenthazard.Thesetreacherouscodingpracticesarethewolvesinsheepsclothing.Whyshouldntyoureferencememoryyouvejustreleased?Whyisitriskytopassdatainglobalorstaticstorage?Whyshouldyouavoidparasiticfunctions?Whyitisunwisetorelyoneverynit-pickydetailoutlinedintheANSIstandard?

8THERESTISATTITUDE
Aprogrammercanfolloweveryguidclineinthisbook，butwithouttheproperattitudeandasetofgoodprogramminghabits，writingbug-freecodewillbemuchharderthanitneedstobe.Ifaprogrammerbelievesthatabugcansimply"goaway，"orthatfixingbugs"later"wontbeharmfultotheproduct，bugswillpersist，ffaprogrammerregularly"cleansup"code，allowsunnecessaryflexibilityinfunctions，welcomesevery"free"featurethatpopsoutofadesign，orsimply"tries"haphazardsolutionstoproblemshopingtohituponsomethingthatworks，writingbug-freecodewillbeanuphillbattle.Havingagoodsetofhabitsandattitudesispossiblythemostimportantrequirementforconsistentlywritingbug-freecode.
EPILOGUEWHEREDOYOUGOFROMHERE?
APPENDIXACODINGCHECKLISTS
APPENDIXBMEMORYLOGGINGROUTINES
APPENDIXCANSWERS
REFERENCES
INDEX
内容简介:
　　《编程精粹编写高质量C语言代码(英文版)》给出了多条编程方面的指导，这些指导看似简单，却是作者多年思考及实践的结果，是对其编程经验的总结。书中解决问题的思考过程对于程序开发人员尤显珍贵。
　　软件日趋复杂，编码错误随之而来。要在测试前发现程序的错误，开发出无错误的程序，关键是弄清楚错误为何产生，又是如何产生。
作者简介:
Stephen A.Maguire，世界著名的技术专家和技术作家。曾在微软公司供职多年，领导开发了Mac版的Excel和众多重要的跨平台项目，并多次扮演救火队员的角色，成功拯救那些陷入困境的团队。现为Web开发公司Storm Development的高级副总裁。他的另一部名著Debugging the Develo
目录:
1AHYPOTHETICALCOMPILER.
Ifyourcompilercoulddetecteverybuginyourprogram——nomatterthetype——andissueanerrormessage，riddingyourcodeofbugswouldbesimple.Suchomniscientcompilersdontexist，butbyenablingoptionalcompilerwarnings，usingsyntaxandportabilitycheckers，andusingautomatedunittests，youcanincreasethenumberofbugsthataredetectedforyouautomatically.

2ASSERTYOURSELF
Agooddevelopmentstrategyistomaintaintwoversionsofyourprogram：onethatyoushipandonethatyouusetodebugthecode.Byusingdebuggingassertionstatements，youcandetectbugscausedbybadfunctionarguments，accidentaluseofundefinedbehavior，mistakenassumptionsmadebyotherprogrammers，andimpossibleconditionsthatneverthelesssomehowshowup.Debug-onlybackupalgorithmshelpverifyfunctionresultsandthealgorithmsusedinfunctions.

3FORTIFYYOURSUBSYSTEMS
Assertionswaitquietlyuntilbugsshowup.Evenmorepowerfularesubsystemintegritychecksthatactivelyvalidatesubsystemsandalertyoutobugsbeforethebugsaffecttheprogram.TheintegritychecksforthestandardCmemorymanagercandetectdanglingpointers，lostmemoryblocks，andillegaluseofmemorythathasnotbeeninitializedorthathasalreadybeenreleased.Integritycheckscanalsobeusedtoeliminaterarebehavior，whichisresponsibleforuntestedscenarios，andtoforcesubsystembugstobereproduciblesothattheycanbetrackeddownandfixed.

4STEPTHROUGHYOURCODE
Thebestwaytofindbugsistostepthroughallnewcodeinadebugger.Bysteppingthrougheachinstructionwithyourfocusonthedataflow，youcanquicklydetectproblemsinyourexpressionsandalgorithms.Keepingthefocusonthedata，nottheinstructions，givesyouasecond，verydifferent，viewofthecode.Steppingthroughcodetakestime，butnotnearlyasmuchasmostprogrammerswouldexpectitto.

5CANDY-MACHINEINTERFACES
Itsnotenoughthatyourfunctionsbebug-free;functionsmustbeeasytousewithoutintroducingunexpectedbugs.Ifbugratesaretobereduced，eachfunctionneedstohaveonewell-definedpurpose，tohaveexplicitsingle-purposeinputsandoutputs，tobereadableatthepointwhereitiscalled，andideallytoneverreturnanerrorcondition.Functionswiththeseattributesareeasytovalidateusingassertionsanddebugcode，andtheyminimizetheamountoferrorhandlingcodethatmustbewritten.

6RISKYBUSINESS
Giventhenumerousimplementationpossibilitiesforagivenfunction，itshouldcomeasnosurprisethatsomeimplementationswillbemoreerrorpronethanothers.Thekeytowritingrobustfunctionsistoexchangeriskyalgorithmsandlanguageidiomsforalternativesthathaveproventobecomparablyefficientyetmuchsafer.Atoneextremethiscanmeanusingunambiguousdatatypes;attheotheritcanmeantossingoutanentiredesignsimplybecauseitwouldbedifficult，orimpossible，totest.

7TREACHERIESOFTHETRADE
Someprogrammingpracticesaresoriskytheyshouldneverbeused.Mostsuchpracticesareobviouslyrisky，butsomeseemquitesafe，evendesirable，becausetheyfillaneedwithoutapparenthazard.Thesetreacherouscodingpracticesarethewolvesinsheepsclothing.Whyshouldntyoureferencememoryyouvejustreleased?Whyisitriskytopassdatainglobalorstaticstorage?Whyshouldyouavoidparasiticfunctions?Whyitisunwisetorelyoneverynit-pickydetailoutlinedintheANSIstandard?

8THERESTISATTITUDE
Aprogrammercanfolloweveryguidclineinthisbook，butwithouttheproperattitudeandasetofgoodprogramminghabits，writingbug-freecodewillbemuchharderthanitneedstobe.Ifaprogrammerbelievesthatabugcansimply"goaway，"orthatfixingbugs"later"wontbeharmfultotheproduct，bugswillpersist，ffaprogrammerregularly"cleansup"code，allowsunnecessaryflexibilityinfunctions，welcomesevery"free"featurethatpopsoutofadesign，orsimply"tries"haphazardsolutionstoproblemshopingtohituponsomethingthatworks，writingbug-freecodewillbeanuphillbattle.Havingagoodsetofhabitsandattitudesispossiblythemostimportantrequirementforconsistentlywritingbug-freecode.
EPILOGUEWHEREDOYOUGOFROMHERE?
APPENDIXACODINGCHECKLISTS
APPENDIXBMEMORYLOGGINGROUTINES
APPENDIXCANSWERS
REFERENCES
INDEX