On Sat, Oct 30, 2021 at 5:03 AM ToddAndMargo via perl6-users <perl6-us...@perl.org> wrote: > > I was trying to get the whole thing in Raku.
Why are you rejecting the "whole Raku" solutions that have been suggested to you in this thread? Your original questions were: * ftp client yet? * Do we have a working ftp module yet? The only answers I've seen are "yes". According to you, the answer was "no". Why do you think that? ---- One suggestion was `LibCurl`. Your response was: > I really need access to the full set of FTP commands, especially > when I am drilling down directories renaming things that won't > delete properly. I can't currently see why curl / `LibCurl` wouldn't give you access to "the full set of FTP commands". Aiui it's "just" a wrapper for a range of protocols, including command/response ones like FTP. `LibCurl` looks robust to me. If you know the author and/or browse the README, the PRs, the issues, and the 2K+ LoC, you will see it is a very well stewarded package that's been continuously improved. Have you installed `LibCurl` and tried it? Curt mentions *another* curl package `Net::Curl`. What about that? ---- The other suggestion was `Net::FTP`. If you know the author and/or browse its README, PRs, issues, and the nearly 2KLoC, you will see it was a well stewarded package that was improved over a 3 year timespan before the author moved on to other PLs. You wrote a comment in an issue of `Net::FTP` in 2017 asking if installing it would be fruitful. The author was appropriately non-committal. Did you try it? A PR by Zoffix was merged a year later. Have you tried it since then? ---- I saw nothing to suggest the authors of these packages would not merge PRs if you provide them. I'm unable to retrieve the License for `LibCurl`, but it appears to be very permissive / public domain. I'm confident the author will provide you with a license document if you wish to read it. The `Net::FTP` license is the excellent Artistic 2, and the author has switched the copyright to TPF. ---- Obviously neither of these packages will perfectly cover everything anyone could ever want from them. That would presumably take a lot more than the mere 3 years of work araraloren put into Raku's `Net::FTP` and 5 years Curt Tilmes has so far put into `LibCurl`. But is your use case really so complicated that these packages don't already cover your use case? ---- Even if they don't yet work for your use case for some reason, why aren't you *improving* these existing packages? They work and they are written in Raku. So what's stopping you using and improving them? ---- I then provided a *third* option that *also* doesn't require that you write *any* Perl code, only Raku code. I did that partly because you'd written: > Can you point me to a paper on how to do that? That suggested you thought it was complicated. It isn't. It's dead simple. (Append a `:from<Perl5>` to a `use` statement.) > the "from perl 5" is cool stuff for sure, but I would still be > maintaining 90% of the code in perl 5. No, you wouldn't. You would get stuff *working* in *Raku* in the *fastest and most efficient way possible*. And *then* you would improve things from there. This would let you *start* with a solid development scenario, with a large test suite to code and test against, and a working solution to compare with your own until you can drop the Perl code. How can that be a bad thing? ---- But perhaps you're saying that, forget *writing* Perl code, you can't cope with even *reading* Perl code, even if it's well written. Not even code that would be essentially *guaranteed* to be *tiny fragments* -- almost all just one or two lines each -- each of which is both *well written* and *fully *documented* (because *all* of them would be *only the code in synopses*). If so, if you can't even *read* single lines of well written Perl code, then fair enough, the `use` Perl approach is a bust. > So it is better just to stay in p5. It sounds like you're saying you'd rather keep *all* your code in Perl, because it's too difficult to *migrate* to Raku step by step. That makes no sense to me. But if that's how you see it, fair enough. ---- I don't understand what you are thinking. I get the impression you don't understand what I'm thinking. So it's now *definitely* time for me to give up. Good luck! -- love, raiph -- love, raiph
