Hi Ben,
On 2017-05-03 14:56, Ben Coman wrote:
Thanks for the follow up. Glad to hear its nothing intrinsic to Pharo.
btw, Is there somewhere in the documentation or class/method comments
that you believe this N-base situation should be spelled out better?
Well, I wouldn't call the parameter of ExternalAddress>>byteAt:...
methods a "byteOffset", as offset invariably indicates a *difference*
between indices or addresses. Thus, I would for example expect an offset
of 0 to refer to the first byte, whether its index is 0 or 1.
This is in contrast with the Smalltalk convention that <something>At:
selectors with numerical arguments usually mean a 1-based *index*.
BTW, just for information, what is your role in the development of Pharo?
Greetings
Raffaello
