On 3/7/2014 12:00 AM, Iain Buclaw wrote:
> I assume the C headers will remain strictly under core.stdc?  So it
> might make sense to transition core.sys -> core.stdc.sys?

I think core.stdc for the Standard C headers can remain the same.

On 7 March 2014 08:34, Walter Bright <newshound2@digitalmars.com> wrote:
> On 3/7/2014 12:00 AM, Iain Buclaw wrote:
>>
>> I assume the C headers will remain strictly under core.stdc?  So it might make sense to transition core.sys -> core.stdc.sys?
>
>
> I think core.stdc for the Standard C headers can remain the same.
>

OK - now that has been sorted.  What's your opinion on where ports of standard C and system C headers should go?

On 3/7/2014 1:03 AM, Iain Buclaw wrote:
> On 7 March 2014 08:34, Walter Bright <newshound2@digitalmars.com> wrote:
>> On 3/7/2014 12:00 AM, Iain Buclaw wrote:
>>>
>>> I assume the C headers will remain strictly under core.stdc?  So it
>>> might make sense to transition core.sys -> core.stdc.sys?
>>
>>
>> I think core.stdc for the Standard C headers can remain the same.
>>
>
> OK - now that has been sorted.  What's your opinion on where ports of
> standard C and system C headers should go?
>

Standard C => core.stdc

Operating system API = > core? core.sys? core.os? I don't have strong feelings about that.

ports of C headers stand for translations of headers from different C libraries: glibc, snn, msvcrt, mingwrt, bionic and should reside in their respective folders like os api interface modules, and stdc will import them conditionally.

On 7 March 2014 09:34, Walter Bright <newshound2@digitalmars.com> wrote:
> On 3/7/2014 1:03 AM, Iain Buclaw wrote:
>>
>> On 7 March 2014 08:34, Walter Bright <newshound2@digitalmars.com> wrote:
>>>
>>> On 3/7/2014 12:00 AM, Iain Buclaw wrote:
>>>>
>>>>
>>>> I assume the C headers will remain strictly under core.stdc?  So it might make sense to transition core.sys -> core.stdc.sys?
>>>
>>>
>>>
>>> I think core.stdc for the Standard C headers can remain the same.
>>>
>>
>> OK - now that has been sorted.  What's your opinion on where ports of standard C and system C headers should go?
>>
>
> Standard C => core.stdc
>
> Operating system API = > core? core.sys? core.os? I don't have strong feelings about that.

Arch ports, not platform ports.

On 7 March 2014 11:25, Kagamin <spam@here.lot> wrote:
> ports of C headers stand for translations of headers from different C libraries: glibc, snn, msvcrt, mingwrt, bionic and should reside in their respective folders like os api interface modules, and stdc will import them conditionally.

Arch, arch, arch! Platform ports are pretty much covered by Walter and Sean's agreement. :)

"Iain Buclaw"  wrote in message news:mailman.27.1394213489.25740.digitalmars-d@puremagic.com...

> Arch, arch, arch! Platform ports are pretty much covered by Walter and
> Sean's agreement. :)

Arch, arch, arch!

https://www.youtube.com/watch?v=5-LIqdjqHts