lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 5698: int->vsize in various alignment and page-layout methods


From: David Kastrup
Subject: Re: Issue 5698: int->vsize in various alignment and page-layout methods (issue 563420043 by address@hidden)
Date: Mon, 27 Jan 2020 16:13:36 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux)

Dan Eble <address@hidden> writes:

> On Jan 27, 2020, at 09:33, David Kastrup <address@hidden> wrote:
>> 
>>> I would like to replace the following with standard types (uint8_t
>>> etc.).  The standard types are portable, but these are not.
> ...
>>>  * flower-proto.hh:typedef unsigned U32;
>>>  * flower-proto.hh:typedef int I32;
> ...
>> I don't really mind here, but "portable" practically means just portable
>> to GCC and Clang which closely follows GCC, so it's not a problem in
>
> I was thinking of differences in data model, e.g. "unsigned" and "int"
> might have as few as 16 bits.  See some examples at
> https://en.cppreference.com/w/cpp/language/types .

None relevant to GCC and Clang as far as I can see.  Can you clarify for
which platforms you expect a practical concern?

-- 
David Kastrup



reply via email to

[Prev in Thread] Current Thread [Next in Thread]