I've written simple Perl bindings to a C++ library using XS++ and Module::Build::WithXSpp. The XS++ code is a single file that defines six classes - nothing fancy, just 80 lines of class and method definitions that directly mirror the C++ API.
My question regards how best to document the distribution using POD. The upper namespace is 'Compress::DSRC'. I currently have a single, auto-generated 'Compress/DSRC.pm' that loads the XS and contains skeleton POD, and clearly I can add documentation here (I've seen POD in XS). However, the classes that users will actually use are e.g. 'Compress::DSRC::Reader' or 'Compress::DSRC::Writer'. Should I create '*.pm' files for each class that contain nothing but POD (other than package declaration, etc?) or is there an acceptable way to document each class within the single 'Compress/DSRC.pm' file?
In reply to Organizing POD for an XS++ module by jdv
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |