Yes, and that in itself is actually going against the point of what I wrote
You gave code that "somebody might choose to customize to meet their needs." I really don't care if telling them what they may need to customise goes against some point you were trying to make.
But you also didn't comment on the main point of my reply
That sometimes, the simplest approach is to role our your own? I have no comment to make about that.
Treating it like a black box is counter to the whole purpose and hints that I failed at conveying the point to you and thus likely to others and so some clarifications were in order.
(Upd: I believe the post-processor mention started in the belief that you might have had more that wasn't shown. As for the pre-processor, that's probably the easiest way to handle the character encoding. )
If the prospective consumer of this example code is unable to determine on their own what the code handles, then they should not be trying to use the code.
Perhaps. I'll have to think about that.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||