Template or Macro

This topic is 1336 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

Recommended Posts

Hi,

Is it better to have a template or macro and why ?

Example of one macro which could be a template :

#define SAFE_DELETE( p ) { delete p; p = NULL; }

Thanks

Share on other sites

"sandwich" is needed to survive, "screwdriver" was not there in paleolithic era and all was fine.

You can look at this link to learn what is paleothic era : http://en.wikipedia.org/wiki/Paleolithic

Edited by Alundra

Share on other sites

There are a few templates in the standard library for safe delete already: here, here and here, for example. So the standard apparently thought it was better to use templates in this case at least.

Edited by Brother Bob

Share on other sites
I think you should prefer templates unless you have a good reason not to.

If you pass an array to SAFE_DELETE it will still compile, but using templates you can force this to give you an error.

int arr[5];
SAFE_DELETE(arr);

Share on other sites

My rule of thumb is to restrict the use of macros constructs that are not related to ordinary c++ code. First example is conditional compilation, i.e. to include or exclude some portions of code that target specific platforms. Another example is assertions, which can't be considered normal code that is supposed to be part of the execution. A third example could be error logging (but that could depend on the context). I'm also using some macros to define and embed shader code inside c++ code.

So in your example, pointer deletion *is* normal code and should *not* use macros. Read up on std::unique_ptr and std::shared_ptr and you'll see that those templates work way better anyway.

Share on other sites

Template when you can, macro when you must.

1. 1
2. 2
Rutin
17
3. 3
4. 4
5. 5

• 13
• 26
• 10
• 11
• 9
• Forum Statistics

• Total Topics
633735
• Total Posts
3013596
×