From: Marcel Holtmann <marcel@holtmann.org>
To: Luiz Fernando Capitulino <lcapitulino@conectiva.com.br>
Cc: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] Re: [RESEND] - Fixes rfcomm program error codes.
Date: Thu, 16 Jun 2005 23:24:01 +0200 [thread overview]
Message-ID: <1118957041.8980.101.camel@pegasus> (raw)
In-Reply-To: <42B1DA59.6040608@conectiva.com.br>
Hi Luiz,
> I sent this patch some days ago, but I saw that my e-mail client
> took the bluez-users address. Hopes to not annoy you sending it
> again (to the right place now).
>
> rfcomm program does not return proper error codes to the environment,
> this makes hard to use it from a shell script or from another program.
>
> Here goes a patch to fix it. I didn't have much time to test it, so
> any feedback is welcome.
>
> - Changes functions to return -1 on error and 0 on success
> - Adds missing error checks
> - Adds missing error messages
> - Fixes rfcomm exit() return codes
I don't see the advantages from changing "exit(1)" into "return -1".
This doesn't fix program error codes.
Regards
Marcel
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-06-16 21:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-16 20:00 [RESEND] - Fixes rfcomm program error codes Luiz Fernando Capitulino
2005-06-16 21:24 ` Marcel Holtmann [this message]
2005-06-16 20:51 ` Luiz Fernando Capitulino
2005-06-16 22:08 ` [Bluez-devel] " Marcel Holtmann
2005-06-17 16:53 ` Luiz Fernando Capitulino
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1118957041.8980.101.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=lcapitulino@conectiva.com.br \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.