-=> Roy J. Tellason wrote to William McBrine <=-

 WM> /* get a little-endian short, return an int */
 WM> unsigned getshort(const unsigned char *x)
 WM> {
 WM>         return ((unsigned) x[1] << 8) + (unsigned) x[0];
 WM> }

 RJT> What's the effect of that "const" in there?

It indicates to the compiler that the value pointed to by x will not be
modified by getshort(). So this function can take both const and non-const
parameters. Without it, one might get a warning when calling it with a
const parameter.

In practice, in this particular context, it doesn't mean much. But I try
always to add "const" to my * parameters, where possible.

... Message contents may settle during uploading.
--- MultiMail/Linux v0.45