Romain Beauxis, le Sun 18 Jul 2010 20:52:54 +0200, a écrit : > I believe you can. You simply have to use #ifndef.
No, because once there is a conflict, the compiled program will mistake one error for the other, and even rebuilding will not detect that in the case of a conflict of another error with some alsa-defined error. > I do not understand not having these values defined. They are explicitely > documented as return values by the libasound. What is the purpose of a > *compatibility* library if you do not make it compatible. But compatibility can not be made to a point where you have things mixed up. The ground problem here is that libasound is defining new values for errno, i.e. touches part of what the system defines, while it should, as other libraries do, define its own way of reporting errors. > Besides, libasound *is* linux-specific, just as those errors, so > adding one but not the other seems a bit inconsistent to me.. It's not: libasound is just a library, not a part of the system. Be it there or not doesn't raise conflicts issues with what the system defines. Samuel -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
