Marcus Crestani <crestani(a)informatik.uni-tuebingen.de> writes:
- memset (l2, 0, sizeof (level_2_lookup_tree));
+ memset (l2, '\0', sizeof (level_2_lookup_tree));
This change will probably not fix any bug. In C, '\0' is another way
to spell 0, and in C++ '\0' will be cast to 0 anyway, since memset's
second argument is int.
Not that I'm against the change -- using '\0' makes the *intention* a
bit clearer -- but it should be applied with understanding that it
doesn't resolve any real problem.
+ memset (&mc_allocator_globals, '\0', sizeof
(mc_allocator_globals_type));
This shouldn't be necessary unless init_mc_allocator is called twice
(which it shouldn't be, judging by the comments and the code). A
global variable is 0-initialized by default and calling memset doesn't
accomplish anything.
Also note that in XEmacs you can spell the above memset as:
xzero (mc_allocator_globals);