StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POC++ how to #define/rename a nested function?
primarykey
Id
14978185
data
AcceptedAnswerId
14978378
AnswerCount
3
ClosedDate
CommentCount
9
CommunityOwnedDate
CreationDate
2013-02-20T11:00:35.693
FavoriteCount
0
LastActivityDate
2013-02-20T12:50:51.223
LastEditDate
2013-02-20T12:50:51.223
LastEditorUserId
1971684
OwnerUserId
1971684
ParentId
0
PostTypeId
1
Score
0
ViewCount
1863
LastEditorDisplayName
text
Body
<pre><code> namespace first { namespace second { class Third { static void foo() { std::cout << "foo\n"; } }; } } void bar() { std::cout << "bar\n"; } #define first::second::Third::foo bar//this doesn't work </code></pre> <p>so, what's the correct way to map a nested function to another one?</p> <h1>Update:</h1> <p>a more similar situation is:</p> <pre><code> struct ReleaseVersion { static void foo() { std::cout << "release version\n"; } }; struct DebugVersion { static void foo() { std::cout << "debug version\n"; } }; #ifdef _DEBUG #define ReleaseVersion::foo DebugVersion::foo #else #define DebugVersion::foo ReleaseVersion::foo #endif </code></pre> <p>what I want to do is just like malloc and _malloc_dbg, when #define _CRTDBG_MAP_ALLOC, in debug mode, malloc will be mapped to _malloc_dbg, and in release mode, _malloc_dbg will be mapped to malloc</p> <h1>Update again</h1> <p>a more more similar situation is:</p> <pre><code> namespace first { namespace second { struct ReleaseVersion { static void foo() { std::cout << "release version\n"; } }; struct DebugVersion { static void foo(const char* file, long line) { std::cout << "debug version\n"; } }; } } #ifdef _DEBUG #define ReleaseVersion::foo() DebugVersion::foo(__FILE__, __LINE__) #else #define DebugVersion::foo(file, line) ReleaseVersion::foo() #endif </code></pre> <p>so, these 2 version of functions may have different parameters, I cannot just call one. I know I can just do this</p> <pre><code> #ifdef _DEBUG #define Foo() first::second::DebugVersion::foo(__FILE__, __LINE__) #else #define Foo() first::second::ReleaseVersion::foo() </code></pre> <p>but in this way, I must always use Foo(), even in the final release mode, it's still a macro. I want to know if there are more flexible way to to do this.</p> <h1>One Solution</h1> <pre><code> #ifdef _DEBUG #define foo() foo(__FILE__, __LINE__) #define ReleaseVersion DebugVersion #else #define foo(file, line) foo() #define DebugVersion ReleaseVersion #endif int main() { first::second::DebugVersion::foo(__FILE__, __LINE__); first::second::ReleaseVersion::foo(); return 0; } </code></pre> <p>it may be dangerous when there are another foo() or RealeaseVersion/DebugVersion in other namespaces, but if you can make sure there won't, I think it can be an acceptable solution.</p>
Tags
<c++><macros>
Title
C++ how to #define/rename a nested function?
singulars
PostAcceptedAnswerId
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USFrahm
UserOwnerUserId
1. USFrahm
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
2. PO
  singulars
  PostTypePostTypeId
  PTAnswer
3. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.