El 28/03/2006, a las 20:43, Tony Lewis escribió:
Hrvoje Niksic wrote:
The cast to int looks like someone was trying to remove a warning and
botched operator precedence in the process.
I can't see any good reason to use , here. Why not write the line
as:
eta_hrs = eta / 3600; eta %=
Greg Hurrell [EMAIL PROTECTED] writes:
El 28/03/2006, a las 20:43, Tony Lewis escribió:
Hrvoje Niksic wrote:
The cast to int looks like someone was trying to remove a warning and
botched operator precedence in the process.
I can't see any good reason to use , here. Why not write the line
hrvoje and i have been recently talking about adding regex support to
wget. we were considering to add a new --filter option which, by
supporting regular expressions, would allow more powerful ways of
filtering urls to download.
for instance the new option could allow the filtering of
what definition of regexp would you be following? or would this be
making up something new? I'm not quite understanding the comment about
the comma and needing escaping for literal commas. this is true for any
character in the regexp language, so why the special concern for comma?
I do like
Mauro Tortonesi [EMAIL PROTECTED] writes:
for instance, the syntax for --filter presented above is basically the
following:
--filter=[+|-][file|path|domain]:REGEXP
I think there should also be url for filtering on the entire URL.
People have been asking for that kind of thing a lot over the
Jim Wright [EMAIL PROTECTED] writes:
what definition of regexp would you be following? or would this be
making up something new?
It wouldn't be new, Mauro is definitely referring to regexps as
normally understood. The regexp API's found on today's Unix systems
might be usable, but
