As software engineers, we are admonished by the doyens of C++ programming that the correct way to report error conditions is to throw exceptions. As game developers, we are the heirs to a vast body of common wisdom holding that exception handling overhead is too expensive for high-performance games, and that error codes are the only acceptable mechanism for propagating errors in game code. What should we believe?
Facebook Joinc 그룹
Joinc QA 사이트
Tweet
joinc는 Firefox와 chrome에서 테스트 했습니다. IE에서는 테이블이 깨지거나 이미지가 보이지 않을 수 있습니다. 특히 구글 Docs이미지의 경우 엑박처리될 수 있습니다.
As software engineers, we are admonished by the doyens of C++ programming that the correct way to report error conditions is to throw exceptions. As game developers, we are the heirs to a vast body of common wisdom holding that exception handling overhead is too expensive for high-performance games, and that error codes are the only acceptable mechanism for propagating errors in game code. What should we believe?
Tweet
joinc는 Firefox와 chrome에서 테스트 했습니다. IE에서는 테이블이 깨지거나 이미지가 보이지 않을 수 있습니다. 특히 구글 Docs이미지의 경우 엑박처리될 수 있습니다.
As software engineers, we are admonished by the doyens of C++ programming that the correct way to report error conditions is to throw exceptions. As game developers, we are the heirs to a vast body of common wisdom holding that exception handling overhead is too expensive for high-performance games, and that error codes are the only acceptable mechanism for propagating errors in game code. What should we believe?
GDC 2006, in San Jose, was my fifth GDC. They're all starting to run together at this point, and this year's GDC was, as always, huge, frustrating, inspirational, boring, fascinating and exhausting in random measure.