BrowserUk,
WOW, I like that shorthand format, N/(N/a*)* and N/(n/a*)* , look very flexible for future encoding/decoding uses.
Until you apply some form of encode/decoding operation to a file or data stream, anything you read is just a bunch of bytes.
This was my take also!
Agreed! I haven't looked at this much, but the spec says '22 bits', but Perl code seems to use '24 bits' for each character with the high-order bits being '00'. Whether other implementations do the same I don't know, but seems like too much room for mis-interpretation.
Thank you
"Well done is better than well said." - Benjamin Franklin
-
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.
|