From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] headerfile depencies
Date: Wed, 20 Apr 2005 14:29:57 +0200 [thread overview]
Message-ID: <1114000197.2469.159.camel@pegasus> (raw)
In-Reply-To: <426649B8.1070203@gmx.ch>
Hi Marco,
> From hluez-libs 2.15 to bluez-libs 2.16, bluetooth.h doesn't anymore
> include the stdio.h (or changes where made and stdio.h went forgotten).
>
> So the user has to include it in his own program, even if he doesn't need it.
> This might be more a c specific question, but aren't header files supposed
> to handle their requirements themselve?
> Please note that I'm not a c expert. This is a question, not a accusation...
I already fixed it in the CVS. I always include stdio.h in my C files
and so this slipped through my eyes.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-04-20 12:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 12:23 [Bluez-users] headerfile depencies Marco Trudel
2005-04-20 12:29 ` Marcel Holtmann [this message]
2005-04-20 12:42 ` Marco Trudel
2005-04-20 12:46 ` Marcel Holtmann
2005-04-27 10:33 ` Marco Trudel
2005-04-27 10:50 ` Marcel Holtmann
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=1114000197.2469.159.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox