Re: [gccsdk] Parsing wget output

On Fri, Sep 21, 2012 at 08:51:05PM +0100, Martin Bazley wrote:
> I think I may need to introduce you to the concept of an "illustrative
> example"...

My apologies. It's been a very long week.

The wget commit log is here:
http://git.savannah.gnu.org/cgit/wget.git/log/
if you want to poke through it to find out if the change was deliberate or a
bug (it's pretty busy).

I think the right answer here is either to use the return value, which as
you say has concurrency issues under RISC OS, or to use curl. IME wget is
more of a UI tool and curl is more of a 'plumbing' tool. Matching the UI
output (as you're doing from wget) is akin to telling a GUI tool to click on
the 4th menu item down - it's fragile and not likely to be stable. (For
starters, what happens in translated versions of wget? I have no idea).

But yes, it does raise the issue of per-process return codes. I'm not sure
of the best way to implement that. DDEUtils perhaps? (like per-process
current directories)

Theo

_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK