[Tcl-bugs] [ tcl-Bugs-991014 ] Missing documentation of octet-char mapping

[SourceForge.net <no...@so...>]

Bugs item #991014, was opened at 2004-07-14 17:58
Message generated for change (Comment added) made by dkf
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=991014&group_id=10894

Category: 12. ByteArray Object
Group: obsolete: 8.4.6
>Status: Closed
>Resolution: Out of Date
Priority: 5
Submitted By: Kristoffer Lawson (setok)
Assigned to: Donal K. Fellows (dkf)
Summary: Missing documentation of octet-char mapping

Initial Comment:
The manpages do not clearly state that when reading in
binary data, f.ex. with [fconfigure -encoding binary]
the string representation is such that each character
in the string is the same as an octet in the original
data. The same applies to [binary format] and anything
else that generates binary data.

The reason this is not self-evident is that equally one
might assume that when binary data is accessed as a
string, the above representation is not made and
instead two octets could form a single character of
unicode.

I am not quite sure what the correct place to document
this behaviour is, as it applies to all binary data (or
anything that is internally a ByteArray object). Still,
this relationship should be made clear.

----------------------------------------------------------------------

>Comment By: Donal K. Fellows (dkf)
Date: 2004-08-03 22:18

Message:
Logged In: YES 
user_id=79902

Already fixed in HEAD. I can't be bothered to backport. :)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=991014&group_id=10894