Actually, UTF8 is not the major issue...it's just one of the tipping points. I have no issues with my UTF8 code, other than tedium in keeping track of it and making sure any new code updates are UTF8 compliant. That tedium would be erased by an all-UTF8 solution, such as Raku offers.
But the bigger issue for me is actually that my code has run into browser-related issues (browsers no longer work as they used to years ago when I started, and now force me to make changes). For example, I have never before used cookies; never needed them, nor wanted them (no need to post those massively annoying and now legally required cookie notices if not using them). Now I am experiencing anomalies because of my hidden-field data, and the updates are a massive headache when subroutines cannot accept named variables. Raku's subroutines do support named variables, which would solve this problem and make my code more maintainable and future-proof.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.