tag:blogger.com,1999:blog-10425945.post114717647952244316..comments2024-03-14T18:15:27.812-03:00Comments on ObjectARX & Dummies: Using MACROS inside ObjectARXFernando Malardhttp://www.blogger.com/profile/09852061806995998594noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-10425945.post-1147361112358940132006-05-11T12:25:00.000-03:002006-05-11T12:25:00.000-03:00Unless you're writing a C++ compiler or something ...Unless you're writing a C++ compiler or something else that could be construed as "the implementation", you’re simply *NOT ALLOWED* to use a name such a _ARX_SGET. It’s not a matter of following "naming conventions", it's about being compliant with the C++ Standard.<BR/><BR/>While there's little need to change existing code that already compiles, at the same time there's no need to implicitly encourage bad practices either--especially when the expectation is that someone will cut-and-paste your code as-is.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-10425945.post-1147275450139987742006-05-10T12:37:00.000-03:002006-05-10T12:37:00.000-03:00Hello,Yes, in fact the idea is only to show what c...Hello,<BR/><BR/>Yes, in fact the idea is only to show what can be done with macros. The macro name and variable naming convention may vary from developer to developer. Some follow global standards and other follow their own standards.<BR/><BR/>Regards,<BR/>Fernando.Fernando Malardhttps://www.blogger.com/profile/09852061806995998594noreply@blogger.comtag:blogger.com,1999:blog-10425945.post-1147273418071342312006-05-10T12:03:00.000-03:002006-05-10T12:03:00.000-03:00Your macros should have names along the lines of "...Your macros should have names along the lines of "ARX_SGET_" or "_arx_sget" instead of "_ARX_SGET" so that they are compliant with the C++ Standard.<BR/><BR/>Identifiers starting with an underscore followed by a capital letter or two underscores are reserved for "the implementation". I avoid the technicalities by simply not using leading underscores.Anonymousnoreply@blogger.com