Alex Bennée writes:
> Markus Armbruster writes:
>
>> Alex Bennée writes:
>>
>>> Markus Armbruster writes:
>>>
Back in 2016, we discussed[1] rules for headers, and these were
generally liked:
1. Have a carefully curated header that's included everywhere first. We
go
Markus Armbruster writes:
> Alex Bennée writes:
>
>> Markus Armbruster writes:
>>
>>> Back in 2016, we discussed[1] rules for headers, and these were
>>> generally liked:
>>>
>>> 1. Have a carefully curated header that's included everywhere first. We
>>>got that already thanks to Peter:
Alex Bennée writes:
> Markus Armbruster writes:
>
>> Back in 2016, we discussed[1] rules for headers, and these were
>> generally liked:
>>
>> 1. Have a carefully curated header that's included everywhere first. We
>>got that already thanks to Peter: osdep.h.
>>
>> 2. Headers should normall
Markus Armbruster writes:
> Back in 2016, we discussed[1] rules for headers, and these were
> generally liked:
>
> 1. Have a carefully curated header that's included everywhere first. We
>got that already thanks to Peter: osdep.h.
>
> 2. Headers should normally include everything they need
Back in 2016, we discussed[1] rules for headers, and these were
generally liked:
1. Have a carefully curated header that's included everywhere first. We
got that already thanks to Peter: osdep.h.
2. Headers should normally include everything they need beyond osdep.h.
If exceptions are need
