Eric Kow <[email protected]> added the comment:
On Sun, Aug 01, 2010 at 18:33:11 +0000, Eric Kow wrote:
> REMARK: Hmm, this sort of stateful way of doing things tends to make me
> nervous (also, do we need to worry about what happens when you call
> wait_next_url several times in parallel?). Could we not return a tuple
> instead? I guess we'd have to find a way to deal with structs in the
> FFI?
I cut out too much context here.
I was referring to this change:
+const int *curl_last_error_num();
which is how we grab the error code from our last attempt to fetch a
URL. I was asking if there is a way we could somehow return this in the
fetch function. Solutions I can think of with my
non-C-programmer-limited brain (*) are some kind of struct or maybe
passing in the error code as a pointer... Maybe somebody wiser can
chime in.
(*) Yeah yeah, kids these days...
--
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
For a faster response, please try +44 (0)1273 64 2905.
__________________________________
Darcs bug tracker <[email protected]>
<http://bugs.darcs.net/patch310>
__________________________________
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
