Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
How to write a macro that discards the const qualifier, for any type?
How to write a macro that discards the const qualifier, for any type?
I hope some combination of typeof and a cast will do, but haven't found the combination.
I tried this, without luck:
#define discard_const(_x) ((typeof(_x + 0)) (_x))
struct t {
char *s;
};
char *
foo(const struct t *r)
{
return discard_const(r->s);
}
I also tried: #define discard_const(_x) ({__auto_type _y = (_x); _y;}), but not luck
The objective is that if I cast to (char *), I fear that if the type of s changes in the future, the cast might silence any warnings, so I want the type to be automatically calculated, and I only want to discard const.
Of course, with pragmas I may disable any const warnings for that specific line, but a macro that does it within the language would be nicer.
2 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
The following users marked this post as Works for me:
| User | Comment | Date |
|---|---|---|
| alx | (no comment) | Jan 7, 2024 at 00:04 |
I developed this macro (using GNU C) similar to C++'s const_cast().
#define const_cast(t, p) \
({ \
static_assert(__builtin_types_compatible_p(typeof(&*(p)), const t)); \
(t) (p); \
})
It asserts that the const version of the specified type is compatible with the type of p. Then it does the cast.
However, as @Lundin said, if you need this macro, you probably have a serious design issue in your code.
0 comment threads
Ignoring the numerous forms of undefined behavior that casting away const might invoke, the blunt but simple and standard solution is just to cast to (void*).
char* foo (const char* str)
{
return (void*)str;
}
This is far more portable than gcc extensions like typeof.
(C23 might introduce various type-related features similar to _Generic so there might be more elegant ways coming soon.)
The only application for these kind of dirty casts is pretty much when dealing with broken API functions that take const-correct parameters but return a non-const pointer, like for example:
char *strstr (const char *s1, const char *s2);
This function is broken by design - always was. Correct design would be to return an index instead of a pointer. But if you are stuck with a broken API such as this one and have to implement it, you have to take shortcuts like casting away const.
2 comment threads