Considering I wrote the Perl programs, there wasn't any need for any scanning of dependencies. Now that I think of it, there was a non-core module that we used: sybperl (Sybase bindings to Perl). I used sybperl instead of DBI because sybperl gives you many of the calls that are available on the C-level as well, which means 1 meter of dead-tree documentation1 (far, far more than DBI/DBD::Sybase), more features, and the ability to quickly prototype (or mimic) something that would later (or was already) written in C or C++ -- the main development languages in the company I then worked for.
1Sybase has (had? I haven't used Sybase for a decade) all its documentation also available online: it keeps (kept?) all its documentation in SGML format, using that as input for both its books and its website. | [reply] |