I would like to add some documentation for the PDL config information in the perldl.conf file and am looking for ideas on a clean way to implement this. The requirements for the approach:
- easy to modify/create/verify by hand - robust against typos, self-checking or reporting errors - beginner-proof - keeps values near their documentation A simple stick POD in place of the commented description lines doesn't work because the hash is assigned in a single statement and perl doesn't like =pod directives to mingle there. 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. Thoughts and ideas welcome! Thanks, Chris _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
