--- - branch: MAIN date: Thu Jul 5 15:17:06 UTC 2012 files: - new: '1.1' old: '0' path: pkgsrc/textproc/p5-Pod-Eventual/DESCR pathrev: pkgsrc/textproc/p5-Pod-Eventual/DESCR@1.1 type: added - new: '1.1' old: '0' path: pkgsrc/textproc/p5-Pod-Eventual/Makefile pathrev: pkgsrc/textproc/p5-Pod-Eventual/Makefile@1.1 type: added - new: '1.1' old: '0' path: pkgsrc/textproc/p5-Pod-Eventual/distinfo pathrev: pkgsrc/textproc/p5-Pod-Eventual/distinfo@1.1 type: added id: 20120705T151706Z.b9b9b06def226968f75053b56719d21c0f2bdd19 log: | Importing packafe for Perl 5 module Pod::Eventual version 0.093330 from CPAN into textproc/p5-Pod-Eventual. POD is a pretty simple format to write, but it can be a big pain to deal with reading it and doing anything useful with it. Most existing POD parsers care about semantics, like whether a =item occurred after an =over but before a back, figuring out how to link a L<>, and other things like that. Pod::Eventual is much less ambitious and much more stupid. Fortunately, stupid is often better. (That's what I keep telling myself, anyway.) Pod::Eventual reads line-based input and produces events describing each POD paragraph or directive it finds. Once complete events are immediately passed to the handle_event method. This method should be implemented by Pod::Eventual subclasses. If it isn't, Pod::Eventual's own handle_event will be called, and will raise an exception. module: pkgsrc subject: 'CVS commit: pkgsrc/textproc/p5-Pod-Eventual' unixtime: '1341501426' user: sno