Marek Rouchal DAT CAD HW Tel 25849 wrote:
>
> I would not want to delete the warnings, I'd prefer an option to suppress
> them or a configurable handler to deal with them (like poderror in
> Pod::Parser).
Sorry, I assumed you'd noticed that most of them are already in Pod::StdParser.
> Pod::Compiler then would do additional checks for proper nesting of =item
> in =over/=back and creating appropriate trees from these commands.
Pod::StdParser does the nesting checks, too.
> This means, if you have room for the destination files, you'll have
> enough for the Storable objects as well.
Only if you delete each Storable-stored file as you generate it's corresponding
output file. Cool.
> However I'd like to ask you to check how fast Pod::Compiler is and whether
> you could live with that.
Not me: my needs are rather light. I'm echoing speed concerns (strongly) felt by
others, and I suspect that you'll merely publish how much faster Pod::Compiler is at
doing POD->HTML, etc., than the existing tools and people will like it.
> Last but not least: I wonder when I'll have some time left for actually
> coding all this ;-)
Yup. Pod::StdParser was trivial compared to what you're working on.
- Barrie
