On 28/04/2005, at 00:23, Jean-Philippe Barrette-LaPierre wrote:

>> I tried this and it still included "-Werror" in the Makefiles which I
>> had to remove manually.
>
> --disable-werror can disable it

I see.

>> Rather than specify this option, I think that the gcc specific warning
>> flags should only be enabled when the compiler has been verified to be
>> gcc rather than having to explicitly turn these flags off.
>>
>
> You're right, but we should do both. We should automaticaly disable
> the "W"
> options when it's not gcc, but we should keep the option to disable it
> manually.

I think this is an excellent strategy.

>> May I ask a quick question?  I'm trying to get the HTTP return status
>> code from a request.  In the libcurl docs, I should be able to get
>> this
>> by calling curl_easy_getinfo() with CURLINFO_RESPONSE_CODE.  I can't
>> see a way to get at that using libcurlpp, I was wondering whether I'd
>> missed something or hasn't that been implemented (yet)?
>
> It hasn't been implemented yet. I'm leaving for one month, and I don't
> have
> the time to do it right now (occupied by the preparatives). In a few
> minutes
> I'll do a release with a function (cURLpp::Easy::getHandle) that will
> return
> the CURL * handle. Then you'll be able to do the getinfo call. But
> remember,
> the CURL pointer will only be valid untill the Easy instance is alive.

I can manage to keep the handle alive in this case so that sounds great
as interim measure.

I have attached another patch to this message which fixes a whole slew
of errors about "Warning: Empty declaration (probably an extra
semicolon)." There were quite a few extra ones in the source, some of
which were extraneous, some of which I would have considered optional.

        Ben.

_______________________________________________
cURLpp mailing list
cURLpp_at_rrette.com
http://www.rrette.com/mailman/listinfo/curlpp