Add package.d files under core

[nordlow]

For the sake of being able to do, for instance,

import core.stdc;

in ImportC.

Shall I go forward with core.sys aswell?

[nordlow]

Why this mak/COPY? Why not just copy everything using a wildcard?!

[nordlow]

Ping.

[dkorpel]

IIRC Walter was against doing this, I'll ask him again.

Either way this needs a good justification. What real world code would benefit from this?

For the sake of being able to do, for instance,

import core.stdc;

in ImportC.

import core.stdc is D, not C or ImportC.

[nordlow]

Just a way for people to more easily make use of all C library standard functions like printf() when using BetterC. So in that case it would suffice to just add the public imports to core.stdc. I'm not sure about core.stdcpp in this regard.

[WalterBright]

Thanks @nordlow for taking the time to do this.

But I have to say, this encourages sloppy programming, and just rubs me the wrong way. In my code, anyway, both C and D, I have no need for most of stdc.

[nordlow]

But I have to say, this encourages sloppy programming

How is this sloppier than already allowed import std?

Thanks @nordlow for taking the time to do this.

But I have to say, this encourages sloppy programming, and just rubs me the wrong way. In my code, anyway, both C and D, I have no need for most of stdc.

The most important addition here core/std/package.d. Enabling

import core.stdc;

in BetterC is IMO a very useful thing.

[nordlow]

Ping.

[nordlow]

import core.stdc is D, not C or ImportC.

I don't understand this statement. The whole purpose of this PR is to have people skilled in C just be able to use most of the common C functions without having to care about in which include/import they reside.

[dkorpel]

I don't understand this statement.

You said:

For the sake of being able to do, for instance,

import core.stdc;

in ImportC.

ImportC is dmd's C compiler. Try creating a .c file with that line in it and compile it with dmd. You will get a syntax error.

How is this sloppier than already allowed import std?

Walter has been against that as well.

The whole purpose of this PR is to have people skilled in C just be able to use most of the common C functions without having to care about in which include/import they reside.

Anyone can write their own utility module which publicly imports all their favorite (C) functions. But for adding features upstream, there's a high bar. You need to show that this feature is pulling its weight, "it might be useful" is not strong enough.

[nordlow]

Ahh, sorry. I meant BetterC usage.

[dkorpel]

Ahh, sorry. I meant BetterC usage.

Even then, it's very easy to translate

#include <stdio.h>
#include <stdlib.h>

To

import core.stdc.stdio;
import core.stdc.stdlib;