| 1 |
* document Pod::POM::View and friends |
| 2 |
|
| 3 |
* add more thorough testing |
| 4 |
|
| 5 |
* fix link generation via L<...> |
| 6 |
|
| 7 |
* handle =encoding |
| 8 |
|
| 9 |
* more views for different styles, formats, etc. |
| 10 |
|
| 11 |
* According to the new podspec: C<< o->foo >> is the same as |
| 12 |
C<o-E<gt>foo>. adjust Pod::POM to handle this kind of markup |
| 13 |
also check that this works: S<C<< $aryref->[$foo] >>> (Most likely |
| 14 |
the text parser needs to be rewritten) [stas] |
| 15 |
|
| 16 |
* you need to escape < and > if they're inside of [A-Z]<...>. Outside |
| 17 |
of formatting code ([A-Z]<...>) the parser shouldn't complain and |
| 18 |
leave < and > as is. |
| 19 |
|
| 20 |
* =begin/=end blocks are mishandled, I have a working version but it's |
| 21 |
imperfect. Parser's rewrite will provide a robust solution [stas] |
| 22 |
|
| 23 |
* some pods may include sequences unrecognized by Pod::POM, currently |
| 24 |
it spits many undefined var warnings (e.g. add N<foo> to the tests). |
| 25 |
- should gracefull handle this situation and probably warn about the |
| 26 |
unknown sequence each time it's encountered with line number. |
| 27 |
- should probably ignore the sequence, but process what's inside the |
| 28 |
sequence like the unknown sequence wasn't there. [stas] |
| 29 |
|
| 30 |
* the =over/=item can have very different usages, currently |
| 31 |
Pod::POM::View::Pod doesn't deparse correctly the following: |
| 32 |
|
| 33 |
=over |
| 34 |
|
| 35 |
=item |
| 36 |
|
| 37 |
Cat |
| 38 |
|
| 39 |
=item |
| 40 |
|
| 41 |
Sat |
| 42 |
|
| 43 |
=item |
| 44 |
|
| 45 |
Mat |
| 46 |
|
| 47 |
=back |
| 48 |
|
| 49 |
it loses the =item parts, simply copy the rest of the item tests I've |
| 50 |
recently added to t/htmlview.t to t/complete.t and you will see that |
| 51 |
the generated pod misses '=item' keys for this section. [stas] |
| 52 |
|
| 53 |
* if the pod doesn't start from the top of the file, but there is some |
| 54 |
leading text, the parser will report warnings on the line numbers |
| 55 |
relative to the beginning of the pod and not the absolute linenumber |
| 56 |
in the file. To make the warnings useful, the parser probably should |
| 57 |
accomodate for skipped non-pod lines. Think of .pm files with |
| 58 |
inlined pod (before each function) where this will come very useful. |