On Fri, Nov 11, 2011 at 10:50 PM, chm <[email protected]> wrote:
> One possibility would be to have all of the > configure file be POD and then generate the > hash data by processing that instead. It would > definitely solve the POD problem but I'm not > sure the best way to keep things from being > too fragile. I'd highly recommend this approach, because there is one source file (the POD with parseable parameters in it). You could have PDL transparently parse older perldl.conf files, and then have PDL recognise the new POD perldl.conf files, and then generate an older perldl.conf (which may be exported to the user). Matt _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
