AutoHotkey Community

It would be nice to have functions like NumGet and NumPut only for strings/raw data.

So basically StrGet would be like SubStr, except it would tolerate NULs in the string.

You can't have nulls in a string because strings are null-terminated. Meaning that if there is a null in the middle of a string, ahk will only see the first half because it thinks that the null marks the end of the string.

It is possible to work with NUL in AutoHotkey. In example with NumGet, which just read one cell from the RAM. It does not matter what data is in here.
Normally, you are right. Ahk just see the first NUL and stops. NUL could be used to safely and fast delimit a list in a standardized way in example.

What is the proposed behaviour of StrGet? All strings in expressions are null-terminated, so the return value of StrGet and incoming parameters of StrPut could not contain NULL characters. (Variable references are an exception since each variable has an internal field which stores the length of its contents.)

I think the use of "Str" in the name of the function implies it works with strings, not necessarily binary data, and "StrGet" does not imply a difference in behaviour to "SubStr".

Perhaps the best solution would be to implement counted strings, allowing explicit null characters (or "zero bytes"). In cases where the length of the string would otherwise need to be calculated, this can also improve performance. Unfortunately it is not a simple matter.

I suggested him to post in Wish List section from here.
http://www.autohotkey.com/forum/topic43222.html

I think StrLen should be to accord with the current behavior