Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   9087 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

__UNCONST(3)		 BSD Library Functions Manual		  __UNCONST(3)

NAME
     __UNCONST — compile time cast-away macro

SYNOPSIS
     #include <sys/cdefs.h>

     void
     __UNCONST(x);

     void
     __UNVOLATILE(x);

DESCRIPTION
     The __UNCONST() macro can be used to omit warnings produced by certain
     compilers when operating with pointers declared with the const type qual‐
     ifier in a context without such qualifier.	 Examples include passing a
     pointer declared with the const qualifier to a function without such
     qualifier, and variable assignment from a const pointer to a non-const
     pointer.  In the same vein, the __UNVOLATILE() macro can be used to
     exclude warnings related to the volatile type qualifier.

IMPLEMENTATION NOTES
     These macros are implemented by explicitly using unsigned long instead of
     intptr_t, a signed type guaranteed to hold a pointer.

SEE ALSO
     cc(1), cdefs(3)

CAVEATS
     As both macros may hide valid errors, their usage is not recommended
     unless there is a well-thought reason for a cast.	A typical use case for
     __UNCONST() involve an API that does not follow the so-called ``const
     correctness'' even if it would be appropriate.  Valid use cases of
     __UNVOLATILE() include passing a volatile pointer to memset(3).

BSD			       December 16, 2010			   BSD

                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 

Vote for polarhome