Re: v5.10.0

On 17 Feb 2008, at 15:00, wil decker wrote: will Crypt::SSLeay build under perl v5.10.0? Yup. The tests pass. Haven't tried using it. -- Andy Armstrong, Hexten

Re: rsync

o how lwp-rget is a replacement for wget http://en.wikipedia.org/wiki/Wget.) Unless I'm misreading the source (which is entirely possible) RsyncP.pm is an implementation of the rsync protocol in Perl + XS. Rsync.pm is indeed just a wrapper around the rsync binary. -- Andy Armstrong, hexten.net

Re: rsync

rt here: http://search.cpan.org/~cbarratt/File-RsyncP-0.52/lib/File/RsyncP.pm Or maybe here: http://search.cpan.org/~leakin/File-Rsync-0.42/Rsync.pm Disclaimer: I haven't used either module -- Andy Armstrong, hexten.net

Re: really low level http, https access

#x27;re talking to a private one or is it publicly available on the 'net somewhere? -- Andy Armstrong, hexten.net

Re: Query Results on Multiple Pages

n multiple pages). How do I write a script that will access the other pages? Find the link to the next page in the source and fetch it. Repeat. -- Andy Armstrong, hexten.net

Re: wget in scripts

ing around with shell scripts or batch files. Also, is there a simple way of constructing the numbers 001-050 for my URL strings? $ perl -e 'system sprintf("wget http://www.for.br/%03d/";, $_) for (1..50);' -- Andy Armstrong, hexten.net

Re: Subclassing HTML::Parser to support $p->include()

_text_. Ah, that's great, thanks. One caveat is that your tag will not be recognized inside tags that force literal text content. For instance: Here will be parsed as text whatever you do. I hadn't thought of that - but I think I can live with it, thanks. -

Re: Subclassing HTML::Parser to support $p->include()

versions of it out too. Thanks. I'm aware of and have used quite a few of the other templating systems include HTML::Template - but I have a bunch of ideas for a template engine that have been brewing for a few years so I'm keen to build this myself. -- Andy Armstrong, hexten.net

Re: Subclassing HTML::Parser to support $p->include()

and then parse that a second time. Ideally though I'd like to handle the include directive at the same stage where I handle my other tags - for various architectural reasons I won't bore you with. Thanks :) -- Andy Armstrong, hexten.net

Subclassing HTML::Parser to support $p->include()

n if it works now it could potentially change in the future - I don't want to rely on undocumented behaviour. So, is what I'm proposing sensible? If not is there a better way? Assuming HTML::Parser currently behaves in the way I need it to is it likely always to do so? Thanks :) -- Andy Armstrong, hexten.net