On 15 November 2017 at 17:09, Jakub Jermář wrote:
> On 11/15/2017 04:43 PM, Jiří Zárevúcky wrote:
>> On 15 November 2017 at 16:36, Jakub Jermář wrote:
>>> On 11/15/2017 04:21 PM, Jiří Zárevúcky wrote:
> Out of curiosity, which C89-only code is being compiled
On 11/15/2017 04:43 PM, Jiří Zárevúcky wrote:
> On 15 November 2017 at 16:36, Jakub Jermář wrote:
>> On 11/15/2017 04:21 PM, Jiří Zárevúcky wrote:
Out of curiosity, which C89-only code is being compiled against libposix?
>>>
>>> libuv compiles as C89. It would probably
On 15 November 2017 at 16:36, Jakub Jermář wrote:
> Hi Jiri,
>
> On 11/15/2017 04:21 PM, Jiří Zárevúcky wrote:
>>> Out of curiosity, which C89-only code is being compiled against libposix?
>>>
>>
>> libuv compiles as C89. It would probably work just fine as C99, but as
>>
Hi Jiri,
On 11/15/2017 04:21 PM, Jiří Zárevúcky wrote:
>> Out of curiosity, which C89-only code is being compiled against libposix?
>>
>
> libuv compiles as C89. It would probably work just fine as C99, but as
> restrict
> shows, compatibility between different C revisions is not a 100% thing,
On 15 November 2017 at 15:59, Vojtech Horky wrote:
> 2017-11-15 15:49 GMT+01:00 Jiří Zárevúcky :
>> On Nov 15, 2017 15:20, "Ondřej Hlavatý" wrote:
>>> strictly speaking, couldn't you define "restrict" a macro in the same
>>>
On Nov 15, 2017 15:20, "Ondřej Hlavatý" wrote:
Hi,
strictly speaking, couldn't you define "restrict" a macro in the same
way then? ;)
You couldn't. "restrict" is a legal identifier in C89, and existing code
can use it e.g. as a regular variable/function name. Identifiers
Hi,
strictly speaking, couldn't you define "restrict" a macro in the same
way then? ;)
OH
On 15.11., Jiří Zárevúcky wrote:
> Hi,
>
> the reason is that "restrict" wasn't a keyword before C99, so those headers
> couldn't be included in code written for C89. __restrict__ is non-standard,
> but
Hi,
the reason is that "restrict" wasn't a keyword before C99, so those headers
couldn't be included in code written for C89. __restrict__ is non-standard,
but that doesn't limit its usability in any way -- if you want to use a
compiler that doesn't support it, you can just define __restrict__ to