On Wed, May 3, 2017 at 10:02 PM, Raffaello Giulietti < [email protected]> wrote:
> 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? > For me Pharo is a dedicated hobby, doing a few hours most week nights and longer stints on weekends. Some people love doing crosswords. I love programming and enjoy Pharo the most. Not having any commercial time pressures has allowed me the luxury to dive deep into areas of interest, which is usually the lower level stuff like DelayScheduler, semaphores/mutexes and Processes in Image & VM - but so far I've not done anything with the JIT. My day job is this... https://www.linkedin.com/in/bencoman/?ppe=1 I dream of one day using Pharo as a soft-realtime industrial automation control system on a Beagleboard, but so far I've taken limited concrete action towards that. I'm located south of the equator in Western Australia, so quite remote from most others in the community (although I did have the pleasure of meeting Thierry & Onil once when they were visiting family here). cheers -ben P.S. I'll take this opportunity to mention I'm between jobs at the moment. So I'd be happy to hear from anyone needing some odd jobs done, while I consider my options.
