tag:blogger.com,1999:blog-1477070468938797157.post85484269158348695..comments2015-10-19T08:55:35.686+02:00Comments on KAI's Blog: Taking apart our first programKAI42http://www.blogger.com/profile/01046465963529739658noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-1477070468938797157.post-8800561653670320562013-02-18T23:16:00.203+01:002013-02-18T23:16:00.203+01:00Aye :DAye :DKAI42https://www.blogger.com/profile/01046465963529739658noreply@blogger.comtag:blogger.com,1999:blog-1477070468938797157.post-80856429189281147072013-02-18T21:20:30.040+01:002013-02-18T21:20:30.040+01:00Ok, got it. The API just uses that #define! So not...Ok, got it. The API just uses that #define! So not your choice. :)root42https://www.blogger.com/profile/13597121138269728177noreply@blogger.comtag:blogger.com,1999:blog-1477070468938797157.post-1224645739543475162013-02-18T21:17:20.138+01:002013-02-18T21:17:20.138+01:00Any particular reason why one would want to use a ...Any particular reason why one would want to use a #define instead of a const? I usually only use const anymore these days. You can even make them static or extern, to your liking. Plus it gives you a bit more type safety, and I think every current compiler should be able to handle them in their optimizations, similar to a #define.root42https://www.blogger.com/profile/13597121138269728177noreply@blogger.com