[Glass] GRPlatform current secureHashFor: depends on the used String class

[Richard Sargent via Glass]

On Tue, Jul 24, 2018 at 1:33 PM, Marten Feldtmann <m at feldtmann.online>
wrote:

> Yes, but this should be made *very* clear in the documentation ...
>

I agree. In retrospect, it isn't surprising. It also is unlikely to be
changed.

The recommended way to do this is to convert the source "string" to UTF-8
and then compute the hash, secure digest, whatever. This is the way to
ensure you get the same results from the Smalltalk image as you do from the
operating system command line for the same string.


> Marten
>
>
> I think one could make a valid argument that the code points should be the
> source of the bits. e.g. ASCII characters in a Unicode16 string would only
> have their ASCII code points used, not the internal representation bits.
>
>
>  Richard Sargent via Glass <glass at lists.gemtalksystems.com> hat am 23.
> Juli 2018 um 21:02 geschrieben:
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20180724/957ba03f/attachment.html>