On 10/26/07, Micah Cowan <[EMAIL PROTECTED]> wrote:
> And, of course, when I say "there would be two Wgets", what I really
> mean by that is that the more exotic-featured one would be something
> else entirely than a Wget, and would have a separate name.
I think the idea of having two Wgets is goo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
With talk of supporting multiple simultaneous connections in a
next-generation version of Wget, various things have been tumbling
around in my mind.
First off is that I would not wish to do such a thing with threads.
Threads introduce too many probl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
> Micah Cowan <[EMAIL PROTECTED]> writes:
>
>> Note that curl provides the additional check for a macro version in
>> the configure script, rather than in the source; we should probably
>> do it that way as well. I'm not sure ho
Micah Cowan <[EMAIL PROTECTED]> writes:
> Note that curl provides the additional check for a macro version in
> the configure script, rather than in the source; we should probably
> do it that way as well. I'm not sure how that helps for this,
> though: if the above test is failing, then either it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel Stenberg wrote:
> On Sat, 27 Oct 2007, Hrvoje Niksic wrote:
>
Do you say that Tru64 lacks both sigsetjmp and siggetmask? Are you
sure about that?
>>>
>>> That is the only system we are currently talking about.
>>
>> I find it hard
Daniel Stenberg <[EMAIL PROTECTED]> writes:
>> It is quite possible that the Autoconf test for sigsetjmp yields a
>> false negative.
>
> I very much doubt it does, since we check for it in the curl
> configure script,
Note that I didn't mean "in general". Such bugs can sometimes show in
one prog
On Sat, 27 Oct 2007, Hrvoje Niksic wrote:
Do you say that Tru64 lacks both sigsetjmp and siggetmask? Are you
sure about that?
That is the only system we are currently talking about.
I find it hard to believe that Tru64 lacks both of those functions;
for example, see
http://h30097.www3.hp.co
Micah Cowan <[EMAIL PROTECTED]> writes:
>> I know nothing of VMS. If it's sufficiently different from Unix that
>> it has wildly different alarm/signal facilities, or no alarm/signal at
>> all (as is the case with Windows), then it certainly makes sense for
>> Wget to provide a VMS-specific run_w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alan Wehmann wrote:
> Fred Holmes cpcug.org> writes:
>
>> If I have a URL that has %20 in place of spaces, and I use the URL directly
>> as
> the argument of WGET, it seems that
>> the file is always "not found". I've discovered that if I replace
Fred Holmes cpcug.org> writes:
>
> If I have a URL that has %20 in place of spaces, and I use the URL directly as
the argument of WGET, it seems that
> the file is always "not found". I've discovered that if I replace each %20
with a space, and put quotation
> marks around the entire URL, it wo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
> Micah Cowan <[EMAIL PROTECTED]> writes:
>
>> Okay... but I don't see the logic of:
>>
>> 1. If the system has POSIX's sigsetjmp, use that.
>> 2. Otherwise, just assume it has the completely unportable, and not
>> even BSDi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
> Zitat von Alan Watt <[EMAIL PROTECTED]>:
>> you connect to TCP port 21 on the proxy server (in the example above,
>> 169.254.1.1)
>>
>> send "USER phred", followed by "PASS xyzzy"
>> send "USER [EMAIL PROTECTED]" followed b
Micah Cowan <[EMAIL PROTECTED]> writes:
> Okay... but I don't see the logic of:
>
> 1. If the system has POSIX's sigsetjmp, use that.
> 2. Otherwise, just assume it has the completely unportable, and not
> even BSDish, siggetmask.
Are you sure siggetmask isn't BSD-ish? When I tested that cod
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
> Micah Cowan <[EMAIL PROTECTED]> writes:
>
>>>We ain't go no siggetmask(). None on VMS (out as far as V8.3),
>>> either, should I ever get so far.
>> siggetmask is an obsolete BSDism; POSIX has the sigprocmask function,
>>
Zitat von Alan Watt <[EMAIL PROTECTED]>:
> The way this particular FTP proxy works, assuming the following:
>
> proxy user name: phred
> proxy user passwd: xyzzy
> proxy server IP: 169.254.1.1
> remote FTP user: sherlock
> remote FTP passwd: holmes
> remote FTP server IP: 30.1
Micah Cowan <[EMAIL PROTECTED]> writes:
> I wasn't really expecting VMS to have sigprocmask(); but I expect
> future systems may conceivably have it and lack the BSD ones (and
> perhaps such systems are already in the wild). Anyway, we'll use
> what's available.
I think you're misunderstanding th
Micah Cowan <[EMAIL PROTECTED]> writes:
>>We ain't go no siggetmask(). None on VMS (out as far as V8.3),
>> either, should I ever get so far.
>
> siggetmask is an obsolete BSDism; POSIX has the sigprocmask function,
> which we should prefer.
We do prefer the POSIX way, which is to use sigset
17 matches
Mail list logo
