[SSSD] [PATCH] silence compilation warnings on RHEL5
Jakub Hrozek
jhrozek at redhat.com
Wed Jul 27 13:51:15 UTC 2011
On 07/27/2011 02:38 PM, Pavel Březina wrote:
> https://fedorahosted.org/sssd/ticket/930
>
>
There's still warnings in some of the sss_ tools coming from assigning
to a "char *" variable from a function returning "const char *". I'm not
actually sure why this warning is only emitted on RHEL5, maybe a
toolchain change? I'd like to avoid using discard_const_p()
unconditionally on all platforms in this case.
Maybe someone might educate me -- what is the point of popt returning
"const char *" if they expect the data to be freed with free(3)? I
thought that traditionally, free functions accept non-const b/c they
might modify the contents of the memory in the process.
I'd like to ACK this unless there are reservations about the warnings in
the tools.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 262 bytes
Desc: OpenPGP digital signature
URL: <https://lists.fedorahosted.org/pipermail/sssd-devel/attachments/20110727/a330f3d4/attachment.sig>
More information about the sssd-devel
mailing list