On Tue, 4 Mar 2008, SF Markus Elfring wrote: > > > This can be done by estabilishing the use of > > __attribute__ ((__warn_unused_result__)) > > I am curious on your approach.
Thanks for the reminder. Now, it went over the list - a few minutes ago. > I assume that some configuration macros might be required for such > compiler-specific extensions. > http://gcc.gnu.org/onlinedocs/gcc-4.2.3/gcc/Function-Attributes.html That documentation page at least does not seem to say so. My approach uses a macro which checks for gcc and its version before enabling it. Maybe that was whay you ment. For example glib's /usr/include/sys/cdefs.h enables its use simply depending on the gcc version and the kernel seems to do so too if ENABLE_MUST_CHECK is turned on. > How often was the option "ENABLE_MUST_CHECK" activated for Linux kernel > compilation already? > http://kernelnewbies.org/KernelJanitors/Todo/ReturnCodes AFAICS, it's enabled in most default configs. Why is that relevant to ntfs-3g when __attribute__ ((__warn_unused_result__)) is already under heavvy use in glibc (inside a gcc version check) already? Bernhard ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ ntfs-3g-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel
