in reply to Hashes made to order

Depending on your current interface layout, it may be a nobrainer to add, or it may turn out quite complex. If the former is the case, I'm not sure why this is such a problem - can you post some code? If the latter is, then I'd concur with chromatic.

Makeshifts last the longest.

Replies are listed 'Best First'.
Re: Re: Hashes made to order
by John M. Dlugosz (Monsignor) on Dec 24, 2002 at 19:26 UTC
    It's for Exporter::VA.

    Basically, when processing the import parameter list, it resolves everything but doesn't actually do it yet. Instead, it keeps a list of name=>ref pairs on a "worklist". Then, a callback is made that may alter this worklist, and finally the worklist is processed.

    So, I have one place where things are added to the list, one place that traverses the list, and maybe places that look things up by name just for warning checking. It might get more later, such as the ability to remove items.

    I'm leaning with chromatic for now, too. As long as I don't box myself into a corner, it should be easy to add later (as another named method) if needed.

    —John

      If this is to be for a CPAN module, then what is wrong with making another CPAN module one of the dependancies?
        I want to push for it to become a standard module. I assume that dependancies on stuff that's not already in there will complicate such ratification.

        —John