> The chief reason is that Perl's documentation format, POD, is actually really > good, unlike Python's documentation format, for example. As such, Perl > programmers have bent their expectations and mode of expression into using > the tool at hand (POD) rather than creating the more expressive notebook > style of documenting things.
you can compare POD to python docstring/doctest, but comparing it to ipython notebooks is completely apples to oranges. notebooks aren't for documenting python code, but rather to document work done using python. you want to use something like POD to document the final, production scripts/code, but something like a notebook is very, very handy for figuring out, documenting, and sharing the steps taken to get there. tim -- +-------------------------------------------------------------------+ | T. E. Pickering, Ph.D. | Southern African Large Telescope | | SALT Astronomer | SAAO | | [email protected] (520) 305-9823 | Observatory Road | | [email protected] +27(0)214606284 | 7925 Observatory, South Africa | +-------------------------------------------------------------------+ overflow error in /dev/null _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
