r2632: a new approach to handling const errors. We have had huge numbers of

const warnings for a long time, and no real way to approach a
solution. Some of them are unavoidable due to the way the C standard
works (for example, any function that provides strchr() like
functionality _must_ produce a const warning)

I will be converting a bunch of places that currently produce const
warnings to use the discard_const_p(). Some of these will be
unavoidable const problems, some of them will be ones we will fix up
over time. At least this change means we will no longer be swamped
with const warnings, and we will easily be able to see when new
problems emerge.
(This used to be commit fec3288ad6ce58e8273e3f16e88037db49ecf046)

1 files changed, 20 insertions, 0 deletions

diff --git a/source4/lib/util.c b/source4/lib/util.c
index c09e1a2997..910a35217c 100644
--- a/source4/lib/util.c
+++ b/source4/lib/util.c
@@ -931,3 +931,23 @@ BOOL all_zero(const char *ptr, uint_t size)
 	return True;
 }
 
+
+/*
+  this is a warning hack. The idea is to use this everywhere that we
+  get the "discarding const" warning from gcc, effectively moving all
+  the warnings to this one place. That doesn't actually fix the
+  problem of course, but it means that when we do get to cleaning them
+  up we can do it by searching the code for discard_const.
+
+  It also means that other error types aren't as swamped by the noise
+  of hundreds of const warnings, so we are more likely to notice when
+  we get new errors.
+
+  Please only add more calls to this function when you find it
+  _really_ hard to fix const warnings. Our aim is to eventually not
+  need this function at all,
+*/
+void *discard_const(const void *ptr)
+{
+	return (void *)ptr;
+}