I know about the long lines. They come from an example that demonstrates automatic clipping if the line length exceeds the terminal width. As you can see from the rest of the pod I did try use propper line lengths. I'll probably have to adjust the "bad" lines considering your comment.

I am a bit reluctant to remove use warnings, but I suppose I could use it while writing the code and comment it just before building the distribution. However to be honest I don't know if the module would work with older perls at all. As far as I can see it should work with 5 and up, but I am not sure about that. Can you tell me which version introduced "use warnings" as a better "-w"?

I only use "our" for the definition of $VERSION. I thought it was appropriate for that. Am I mistaken? Everything else should be strictly private to the package itself.

About the pod. What's the consensus around here? I am used to writing it after _END_ mostly because I feel it makes the code less cluttered. I always try to write the code itself as clear as possible, even at the cost of some performance, because most of the time others have to use it after I've written it and they might not be equally at home with Perl as me or the people frequenting this site. I don't have a problem with putting the attribute and method related parts next to the pieces of code they relate to. But this way it is all bundled together. To the users it shouldn't matter anyway as they'll probably only read it through pod2xxx or perldoc.

I would like to test everything, but I just can't think of ways to test the menu's functionality. How do you verify a terminal supports ANSI sequences? Or really does return the keycodes I am using? I could use some hints on this one...

Thanks for your comments. I am off now to start reading the page behind the link to Tie::PureDB now.