* [Bluez-users] better return code handling in rfcomm command
@ 2003-01-10 15:40 wim delvaux
0 siblings, 0 replies; only message in thread
From: wim delvaux @ 2003-01-10 15:40 UTC (permalink / raw)
To: BlueZ Mailing List
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
Hi all,
just found out that some errors do not cause rfcomm to retrun with exit != 0
It seems that the 'func' field in the command jump table should return int and
not void.
All commands can then return an error code (probably one that was generate by
an deeper function) and cause exit to return proper return values.
Patch attached
[-- Attachment #2: patch.gz --]
[-- Type: application/x-gzip, Size: 1215 bytes --]
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-01-10 15:40 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-01-10 15:40 [Bluez-users] better return code handling in rfcomm command wim delvaux
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.