Dean Roddey
04-28-2009, 04:20 PM
For 3.0, the driver 'backdoor' commands that take a number to indicate the command, the value to query, etc... have been changed to use a string. Not very many drivers use these, and most that do are CQSL written drivers. I've fixed all of the drivers that ship with the product, but others will need to be fixed as well.
So if you use any of these commands in your driver, you'll need to change them. The fix is trivial really. Just change the method to take a string and change the value being passed to be a string that has some self documenting value.
This will of course break any clients that use it. This is unfortunate, but this needs to be done and the number of clients that use such clients is going to be pretty small, and of those the number of them that they'd use will be pretty small as well. Mostly they are only used internally.
So anyway, this will be a breaking point with 2.4.40. Anyone beyond that is going to fail to compile your driver correctly until this change is made. So there may be a wee period of pain. But it would have been worse and worse the long we waited. And the nature of these operations doesn't make it very practical to try to automatically update them during the upgrade, because the values that need to be changed are only known to the drivers.
So it'll just have to be suffered through, though the ease of the changes should make it fairly quickly to get through. And these changes will make these commands much safer, more self-documenting, and extensible in the future.
So if you use any of these commands in your driver, you'll need to change them. The fix is trivial really. Just change the method to take a string and change the value being passed to be a string that has some self documenting value.
This will of course break any clients that use it. This is unfortunate, but this needs to be done and the number of clients that use such clients is going to be pretty small, and of those the number of them that they'd use will be pretty small as well. Mostly they are only used internally.
So anyway, this will be a breaking point with 2.4.40. Anyone beyond that is going to fail to compile your driver correctly until this change is made. So there may be a wee period of pain. But it would have been worse and worse the long we waited. And the nature of these operations doesn't make it very practical to try to automatically update them during the upgrade, because the values that need to be changed are only known to the drivers.
So it'll just have to be suffered through, though the ease of the changes should make it fairly quickly to get through. And these changes will make these commands much safer, more self-documenting, and extensible in the future.