On 2019-07-01, A  Dumas  wrote:

> The Natural Philosopher  wrote:
>
>> On 01/07/2019 10:59, Richard Kettlewell wrote:
>>
>>> The Natural Philosopher  writes:
>>>
>>>> On 01/07/2019 08:32, Richard Kettlewell wrote:
>>>>
>>>>> The Natural Philosopher  writes:
>>>>>
>>>>>> On 30/06/2019 21:02, Richard Kettlewell wrote:
>>>>>>
>>>>>>> For both Intel and ARM the 64-bit instruction sets double the number of
>>>>>>> architectural GPRs.
>>>>>>
>>>>>> Ground penetrating radars?
>>>>>
>>>>> General Purpose Registers.
>>>>
>>>> I know that. But who else does?
>>>
>>> People who are interested enough in assembly language to learn some of
>>> the associated terminology.
>>>
>>> (People are aren’t interested in assembly presumably don’t care about
>>> the detailed differences between instruction sets.)
>>
>> Ok, but there is a lot of assumption in there :-)
>
> E.g. I used to do assembler programming (long ago) but only after saw the
> explanation did I go: ah yes.

This brings us to an important rule of writing: if you're going to use
an acronym or abbreviation - especially if it's not in wide use - write
it out in full the first time, preferably followed by the abbreviation
in parentheses.  Afterwards you can use the abbreviation alone and the
reader will be sure to know what it means.

If you're only using the term once, don't waste your (or the reader's)
time by abbreviating it at all.

--
/~\  cgibbs@kltpzyxm.invalid (Charlie Gibbs)
\ /  I'm really at ac.dekanfrus if you read it the right way.
 X   Top-posted messages will probably be ignored.  See RFC1855.
/ \  Fight low-contrast text in web pages!  http://contrastrebellion.com

--- SoupGate-Win32 v1.05