[MPEG-OTSPEC] SHORT vs int16 vs ???

[Behdad Esfahbod]

On Fri, Aug 14, 2020 at 2:19 PM Dave Crossland <dcrossland at google.com>
wrote:

>
>
> On Fri, Aug 14, 2020 at 1:36 PM Behdad Esfahbod <behdad at behdad.org> wrote:
>
>> On Fri, Aug 14, 2020 at 7:40 AM Eric Muller <eric.muller at efele.net>
>> wrote:
>>
>>> At the same time, the names of structures in OpenType tables end up in
>>> code, documentation, tools' UI, discussions on this list, our heads, etc..
>>> Changing them every two months is not going to help. I would prefer such
>>> changes to occur infrequently, may be accumulating them in a backlog in the
>>> mean time.
>>>
>>
>> Not just that: Peter's unilateral renaming was a disservice to the
>> specification: he replaced the obscure-looking "SHORT", "USHORT", "LONG",
>> "ULONG", with common words "int16", "uint16", "int32", "uint32", even
>> though those do not match the similarly-named types in computers and
>> languages, because the OpenType ones are always big-endian.  If he had
>> consulted others, we could have reached a universally-unambiguous and clear
>> names.
>>
>
> What alternatives do you propose, Behdad, Peter, Eric, anyone? :)
>

BEInt16, BigInt16, ..

I know matches my initial, but not what I suggest. :-)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.aau.at/pipermail/mpeg-otspec/attachments/20200814/552d3f60/attachment-0001.html>