Hi Marcel,
it's possible use uint32 without problems.
- 0x00000000 - 0x000000FF Bluetooth error codes (current situation)
- 0x00000100 - 0x0000FFFF Reserved for future Bluetooth error codes extension
- 0x00010000 - 0x0001FFFF D-Bus errors
- 0x00020000 - 0x0003FFFF System errors (0x00020000 + system error value)
- 0x00040000 - 0xFFFFFFFF Reserved to future error classes
In order to make easier discover the error type, I defined the error values range
considering bitwise operations.
Regards,
Claudio.
On 9/28/05, Marcel Holtmann <marcel@holtmann.org> wrote:
Hi Claudio,
> 2. Use error ranges
> Define only one error message name(org.bluez.EFailed), signature:
> sq
> - 0x0000 - 0x00FF Bluetooth error codes
> - 0x0100 - 0x01FF D-Bus errors
> - 0x0200 - 0x02FF System errors (0x0200 + system error value)
> - 0x0300 - 0xFFFF reserved to future error classes
I like to go with this approach and a name like org.bluez.Error, because
this makes it easy to map the Bluetooth errors. Question is if we should
use uint16 or uint32. Maybe the Bluetooth specification extend their
error codes to an uint16 instead of an uint8 and then I like to have a
free space in this range. Do you think this is a problem?
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more.
http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel