I would agree the example could be better, and I will work on a construct that should highlight the intent of the construct, and a better explanation of the construct.Īsking people to comment the entire book was not my intention. Sorry about that, but I don't mind any feedback. Changing it would remove the point of not raising exceptions if it can be avoided with simple if-statements, and it will remove a little hint on how to protect multiple resources. I took a look at the code, and there is nothing wrong with the example. ![]() If you'd like people to comment on the entire book, do ask! That said, I'd strip out the FileExists check and just focus on the exception handling: it's just a couple of minor inaccuracies. I don't think the issue is complexity, the example is fine. I hope this can be of some help in a more pragmatic view of coding styles, or a more professional approach to style guides. Being a free book proofreading by professionals in English was not and option. This book is free and although written in English, it is not my mother tongue, and thus lacking proofreading. Obviously, it takes some time to write a book, and the experience will determine a pursue into 3-4 other titles about programming. ![]() Being a Certified Delphi Developer I would of course prefer a formalized style guide, but with colleagues rarely aware of style guides available, it has been difficult to work in environments with changing degree of arbitrariness.īeside raising awareness of available style guides, the book has been an exercise in writing a book. I wrote a book about style guides for Object Pascal, after so many years in different projects with different approaches into coding style. ![]() I know this is a controversial topic, but nonetheless it deserves some attention.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |