Re: [SEPOL] Const in APIs (part 1)

[Ivan Gyurdiev <ivg2@cornell.edu>]

>> Makes a ton of things const for the purposes of enhanced error checking.
>>
>> I can't figure this out out:
>> context.c: In function ‘sepol_check_context’:
>> context.c:25: warning: passing argument 1 of ‘sepol_context_to_sid’ 
>> discards qualifiers from pointer target type
>>
>> Something's confusing it - either the hidden proto, or the fact that the 
>> typedef wraps the pointer - not sure why it won't go away.
>>     
>
> I added an explicit type cast to silence it.
>   
... but that's cheating! Why does it really occur?
The whole point of the const types is to reveal bugs, which you are 
hiding by casting..



--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.