Hi, Martyn Pearce: > Mark Mielke writes: > | I never suggested that backwards compatibility be sacrificed. I suggest > | that the code should eventually be fixed. MajorDomo is one of those tools > | that hasn't been touched in years (unless I'm wrong here), and NEEDS > | some clean up. > Majordomo is a bad example -- it's getting more and more useless every day. > So, why does it "NEED" some clean up? Ain't broke, don't fix, yadda > yadda. > It _is_ broken. A "normal" Perl programmer could wrap their mind around the code a few years ago, but today the first thing I'd do if I had to fix a nontrivial Majordomo problem would be to global-replace every single instance of main' with main::, to rewrite the whole thing to use $data{$adress}{key} instead of $key1{$address} through $key99{$address}, and to modularize the whole thing -- simply because I wouldn't trust my understanding of the beast otherwise. That's a _lot_ of work. This is not exactly on-topic, but we found that it's a whole lot cheaper _and_ a whole lot faster to take a spare machine, install linux+mysql+ +qmail+ezmlm-idx on it, and *bingo* you have a fast mailing list manager with a database backend and automatic bad-address tracking, instead of a clunky fossil which is none of these things. -- Matthias Urlichs | noris network GmbH | smurf@noris.de | ICQ: 20193661 The quote was selected randomly. Really. | http://www.noris.de/~smurf/ -- Do what I mean, not what I say!