If people bothered to write code that validates input to functions, why disable it? The only reasons that I can see are:
When the callers behave correctly, every such test wastes CPU cycles.
And when every layer has such tests in multiple places, the costs do start to add up. It's not individual checks that slow things down (and fatter code does reduce cache efficiency), but in the aggregate having lots of tests will easily add up. Notice how the functions in linux/lib/string.c don't bother to check for null pointers, as one example. - Dave ------------------------------------------------------- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
