Hi! On Thu, Sep 23, 2004 at 08:51:01PM +0100, Graham Barr wrote:
> An issue I would have with that code snippet is that line information > of the original code is lost. I don't know your reasons for wanting > to remove the POD, so it may not be an issue for you. But if you > simply just remove the POD from the file, correlating any warning > back to the original source will require inspecting the stripped file. I do not care about the line numbers. I'm currently (again) writing a Parse::RecDescent based parser to extract use statments from Perl code: http://search.cpan.org/~domm/Module-ExtractUse-0.10/ (the CPAN version is old, I'm about to release a new version...) I do not want the POD to interfere with this. Therefor, I wish to remove it. The reason I do all this is to have CPANTS report what modules are actually used by a distribution (remember, CPANTS cannot run code (=inspect the symbol table)). > If this is an issue for you, then I suggest looking at how > Module::Install > solves this problem. I'll take look at it > Pod::Strip would be my preference. ok. Thanks for the Feedback. -- #!/usr/bin/perl http://domm.zsi.at for(ref bless{},just'another'perl'hacker){s-:+-$"-g&&print$_.$/}
