ny order).", 5, &call_id_string, 1},
                                                                                                                                    ^
    
    sipp.cpp(247): error: a value of type "const char *const *" cannot be used to initialize an entity of type "void *"
       {"stat_delimiter", "Set the delimiter for the statistics file", 5, &stat_delimiter, 1},
    
    just add casts to (void *) after taking the addresses.
    
    Also please use the gcc-help@ list for such questions, not bugzilla.
    
    Thanks.

[ Comment 4 ](show_bug.cgi?id=35233#c4) Markus Elfring  2008-02-17 15:52:08
UTC

    
    
    (In reply to [comment #3](show_bug.cgi?id=35233#c3))
    > The problem is here:
    > sipp.cpp(137): error: a value of type "const char *const *" cannot be used to
    > initialize an entity of type "void *"
    >    {"cid_str", "Call ID string (default %u-%p@%s).  %u=call_number,
    > %s=ip_address, %p=process_number, %%=% (in any order).", 5, &call_id_string,
    > 1},
    >                                                                                
    >                                                 ^
    
    Thanks for your suggestion.
    
    
    > sipp.cpp(247): error: a value of type "const char *const *" cannot be used to
    > initialize an entity of type "void *"
    
    How did you get this error message? It is different from mine.
    
    Each array element is initialised by five values that were not flagged with errors before my source code refactoring. Well, I'm sorry - The initialisation list was too long for me to remember that I updated the data type for two other global variables that were referenced from the included source file "sipp.hpp". The message did not point me to my error directly. I suggest to improve the wording from "an entity" to "entity 'data'" in my use case.
    struct sipp_option {
    	const char *option;
    	const char *help;
    	int type;
    	void *data;
    	int pass;
    };
    
    
    > just add casts to (void *) after taking the addresses.
    
    The specification "void const* data;" would be another design option. It might not be clear yet which way will be preferred for the concrete application.

[ Comment 5 ](show_bug.cgi?id=35233#c5) Richard Biener  2008-02-17 15:55:27
UTC

    
    
    I used the Intel compiler to point me to the actual error.

[ Comment 6 ](show_bug.cgi?id=35233#c6) Markus Elfring  2008-02-17 16:11:07
UTC

    
    
    It was hard for me to spot the updated variables "stat_delimiter" and "call_id_string" as the error reasons.
    
    It would be nice if the GCC implementation will be even more precise than the check with the Intel compiler. How do you think about better error indicators?

[ Comment 7 ](show_bug.cgi?id=35233#c7) Richard Biener  2008-02-17 16:41:43
UTC

    
    
    Well, certainly.  We possibly already have an enhancement request for this.

[ Comment 8 ](show_bug.cgi?id=35233#c8) Markus Elfring  2008-02-17 17:17:17
UTC

    
    
    I am curious on improvements for unambiguous error reporting with variable and member names.

|  
---|---  
  
* * *

  * [ Format For Printing ](show_bug.cgi?format=multiple&id=35233)
  * \- [ XML ](show_bug.cgi?ctype=xml&id=35233)
  * \- [ Clone This Bug ](enter_bug.cgi?cloned_bug_id=35233)
  * \-  Top of page 

  

  *     * [ Home ](./)
    * |  [ New ](enter_bug.cgi?product=gcc)
    * |  [ Browse ](describecomponents.cgi)
    * |  [ Search ](query.cgi)
    * |  [ [?] ](page.cgi?id=quicksearch.html "Quicksearch Help")
    * |  [ Reports ](report.cgi)
    *     * |  [ Help ](https://bugzilla.readthedocs.org/en/5.0/using/understanding.html)
    * |  [ New Account ](createaccount.cgi)
    * |  [ Log In ](show_bug.cgi?id=35233&GoAheadAndLogIn=1) Remember  [x] 
    * |  [ Forgot Password ](show_bug.cgi?id=35233&GoAheadAndLogIn=1#forgot) Login:  [x]