Re: No warning at implicit removal of const. Was: relearning C: why does an in-place change to a char* segfault?

"Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> writes:

For some reason I had a sort of a habit wrt const pointers:
>
(experimental code, no ads, raw text...)
https://pastebin.com/raw/f52a443b1
>
________________________________
/* Interfaces
____________________________________________________________________*/
#include <stddef.h>
>
>
struct object_prv_vtable {
  int (*fp_destroy) (void* const);
};
>
>
struct device_prv_vtable {
  int (*fp_read) (void* const, void*, size_t);
  int (*fp_write) (void* const, void const*, size_t);
};

Why?  It seems like an arbitrary choice to const qualify some pointer
types and some pointed-to types (but never both).

;^)

Does the wink mean I should not take what you write seriously?  If so,
please ignore my question.

--
Ben.