comment on

I can't tell much about implementation or API, cause it's very complicated.

You might want to discuss this on P5P.

Otherwise ... in order to have deeper insight and better feedback here, could you please provide a list of hands on examples of what you see and what you want?

> Even if it's too low priority to fix code, maybe stream-lining documentation would be not too much work

Well I think you are always welcome to provide patches to perldoc.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

In reply to Re^3: (Some) inconsistencies with IO built-ins, their documentation and filehandle names ("symbolic references") by LanX
in thread (Some) inconsistencies with IO built-ins, their documentation and filehandle names ("symbolic references") by vr

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Pathologically Eclectic Rubbish Lister
	PerlMonks