... since you likely can't embed pod in a .c source file.
You can use POD in any language that has multiline comments. In the case of C you'd just put your POD between the /* ... */ markers.
To your specific question, I always put the POD right in the code, and use Test::Pod and Test::Pod::Coverage to make sure the POD follows some type of standard. In my application's t/ directory I always put the following files:
$ cat t/02pod.t use strict; use warnings; use Test::More; eval "use Test::Pod 1.14"; plan skip_all => 'Test::Pod 1.14 required' if $@; plan skip_all => 'set TEST_POD to enable this test' unless $ENV{TEST_P +OD}; all_pod_files_ok(); $ cat t/03podcoverage.t use strict; use warnings; use Test::More; eval "use Test::Pod::Coverage 1.04"; plan skip_all => 'Test::Pod::Coverage 1.04 required' if $@; plan skip_all => 'set TEST_POD to enable this test' unless $ENV{TEST_P +OD}; all_pod_coverage_ok();
In other words, I dont recommend putting POD in its own file for application documentation.
regards,
In reply to Re: Some clarification where pod files should reside in a distro
by trwww
in thread Some clarification where pod files should reside in a distro
by leocharre
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |