On Mon, Dec 24, 2018 at 05:06:13PM +, i...@sdf.org wrote:
> > For practical reasons we restrict c89 + extensions to building tools.
>
> what is intended by "tools"?
This is the part that is needed for bootstrapping our cross build environment.
Once "tools" are compiled, they are used to build
> For practical reasons we restrict c89 + extensions to building tools.
> For the rest we prefer gnu99.
If we still restrict to c89,
does that mean (in majority) there are no keywords
"inline", "restrict", "_Bool", "_Complex" or "_Imaginary"?
(Note that I barely know what are extended by GNU.)
I be
On 24.12.2018 17:09, Gua Chung Lim wrote:
>> For practical reasons we restrict c89 + extensions to building tools.
>> For the rest we prefer gnu99.
> If we still restrict to c89,
> does that mean (in majority) there are no keywords
> "inline", "restrict", "_Bool", "_Complex" or "_Imaginary"?
The r
On 24.12.2018 18:06, i...@sdf.org wrote:
>> For practical reasons we restrict c89 + extensions to building tools.
>
> what is intended by "tools"?
>
src/tools
signature.asc
Description: OpenPGP digital signature
> For practical reasons we restrict c89 + extensions to building tools.
what is intended by "tools"?
On 24.12.2018 15:46, i...@sdf.org wrote:
> is netbsd still using c89 for a majority of it's core?
> if yes, approximately how much percent would that be?
>
For practical reasons we restrict c89 + extensions to building tools.
For the rest we prefer gnu99.
signature.asc
Description: OpenPGP dig
is netbsd still using c89 for a majority of it's core?
if yes, approximately how much percent would that be?
