in reply to Re: perl script to compare two directories
in thread perl script to compare two directories

Yeah, probably a dir compare script isn't a very complex program, and I will be able to do it in a few hours ...BUT I remember asking earlier for perl scripts that others have made. I wanted to see what's out there, and what kind of free perl scripts I can use that others have written. And I was told that if I install Linux, it comes with a bunch of perl scripts as part of the installation. I don't use Linux, but maybe some of you do. And maybe if Linux comes with a free Perl script that compares directories, then someone will let me know. I just wanted to see the work others have done before I get to it myself. If a dir compare script is such a novel idea that no one has it, then I guess I will write one and share it here for free. Lol
  • Comment on Re^2: perl script to compare two directories

Replies are listed 'Best First'.
Re^3: perl script to compare two directories
by GrandFather (Saint) on Jul 12, 2019 at 05:42 UTC

    I'm sure its been done many times before in many different ways for many different reasons. I've even done something like that myself: Directory tree explorer with stats reporting

    Reading other people's code is often a good way of learning. But without guidance what you learn can often just be bad habits. Trying yourself then coming here for comment is likely to help you learn faster and better.

    Optimising for fewest key strokes only makes sense transmitting to Pluto or beyond
Re^3: perl script to compare two directories
by marto (Cardinal) on Jul 12, 2019 at 05:58 UTC

    It was previously pointed out that using an abandoned version of a cut down build of perl, which hasn't had an update since 2003 isn't a great starting point. Strawberry perl was recommended. This comes with scripts as part of the installation, which is besides the point. You don't have to run Linux at all. Secondly a web search will find you many examples of why you're looking for. Besides being completely wrong in you assertions the last time this was discussed, you've needlessly over complicated the proposed specification here.