in reply to Re: Moving from hashing to tie-ing.
in thread Moving from hashing to tie-ing.

If it were me in this situation, I would leave the ugly-but-working code intact to handle current processing. I would then study it thoroughly to determine the original specs of the project. I would then reverse-engineer a ground-up rewrite of the code using those specs.

That way, you're not constrained by any legacy code conventions and can do it your way right from the start. You have the added advantage of a more relaxed time-frame, since the current code is still working in the production environment.

---
It's all fine and dandy until someone has to look at the code.

Replies are listed 'Best First'.
Re^3: Moving from hashing to tie-ing.
by eff_i_g (Curate) on Aug 02, 2006 at 19:13 UTC
    I'm in agreement with your approach kwaping, thank you. Well, at least I learned a little bit about tie through this whole debacle: don't use it on huge files; and I started reading the chapter.

    When and if the rewrite takes place, I think putting the data back into a database is the way to go. Some advanced SQL statements would eliminate a great deal of the Perl coding. I'll see.

    Thanks for your time.
[reply]

In Section Seekers of Perl Wisdom