[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [libmicrohttpd] src/daemon/response.h virtually empty
From: |
Christian Grothoff |
Subject: |
Re: [libmicrohttpd] src/daemon/response.h virtually empty |
Date: |
Fri, 6 Aug 2010 14:26:26 +0200 |
User-agent: |
KMail/1.13.2 (Linux/2.6.32-24-generic; KDE/4.4.2; i686; ; ) |
On Thursday, August 05, 2010 09:33:24 pm Amr Ali wrote:
> Version: 0.9.0
>
> Why is `src/daemon/response.h' does not contain function declarations of
> `src/daemon/response.c'?
Simple, most of those are part of the public API and hence in 'microhttpd.h'.
> I'm developing some module internally for MHD, I understand that I can make
> use of the functions inside `response.c' without having a `response.h'
> referencing functions' signatures, and it would do just fine at compile
> time. But it is kind of awkward to do things that way.
No, you should just #include 'microhttpd.h'. The only reason why 'response.h'
exists is that there is one function that is defined in 'response.c' which is
not considered public (since I don't think it is generally useful and I like
minimal APIs) and we need it in 'daemon.c'.
> If you won't mind I can put all the functions prototypes inside
> `response.h'.
No, they are in 'microhttpd.h' and you should simply include that header.
Don't prototype them twice.
Happy hacking,
Christian
> Best regards,
> Amr Ali - Security Engineer