On Mon, Jun 02, 2014 at 12:33:14PM -0400, Ted Unangst wrote: > What compiler warns about this? It's perfectly fine to pass a nonconst > string to a function that takes a const string.
char * vs unsigned char *? Joerg
- [PATCH 2/7] fix type string conversion warning Brent Cook
- [PATCH 3/7] remove unused static datastructures Brent Cook
- [PATCH 7/7] avoid defining struct pqueue typedef twice Brent Cook
- Re: [PATCH 7/7] avoid defining struct pqueue typed... Philip Guenther
- [PATCH 5/7] do not include public headers as though the... Brent Cook
- [PATCH 6/7] remove parsing of -rand options in openssl ... Brent Cook
- Re: [PATCH 2/7] fix type string conversion warning Ted Unangst
- Re: [PATCH 2/7] fix type string conversion warning Joerg Sonnenberger
- Re: [PATCH 2/7] fix type string conversion warning Ted Unangst
