From bd8acf91e69788e2f13c8f34fda0b8039067b83a Mon Sep 17 00:00:00 2001 From: Fabian Keil Date: Sun, 4 Mar 2012 11:48:34 +0000 Subject: [PATCH] Fix hash_string()'s description As far as Privoxy is concerned the function only has one use case. Whether or not it's anyone's favorite is not particularly important. Also the documented return code type didn't match reality. --- miscutil.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/miscutil.c b/miscutil.c index 1e0a647e..b45490e4 100644 --- a/miscutil.c +++ b/miscutil.c @@ -1,4 +1,4 @@ -const char miscutil_rcs[] = "$Id: miscutil.c,v 1.68 2011/09/04 11:10:56 fabiankeil Exp $"; +const char miscutil_rcs[] = "$Id: miscutil.c,v 1.69 2012/03/04 11:41:57 fabiankeil Exp $"; /********************************************************************* * * File : $Source: /cvsroot/ijbswa/current/miscutil.c,v $ @@ -135,13 +135,12 @@ void write_pid_file(void) * Function : hash_string * * Description : Take a string and compute a (hopefuly) unique numeric - * integer value. This has several uses, but being able - * to "switch" a string the one of my favorites. + * integer value. This is useful to "switch" a string. * * Parameters : * 1 : s : string to be hashed. * - * Returns : an unsigned long variable with the hashed value. + * Returns : The string's hash * *********************************************************************/ unsigned int hash_string( const char* s ) -- 2.39.2