I want to import a module from my local project  in C style (#include "local.h").

I know I can do "dmd main.d local.d" but I wonder if it can be done C style.

Thank you

BD

On 6/25/15 9:57 AM, Binarydepth wrote:
> I want to import a module from my local project  in C style (#include
> "local.h").

No.

>
> I know I can do "dmd main.d local.d" but I wonder if it can be done C
> style.

What is your goal? Why doesn't D import work for you?

-Steve

On Thursday, 25 June 2015 at 14:10:00 UTC, Steven Schveighoffer wrote:
> On 6/25/15 9:57 AM, Binarydepth wrote:
>> I want to import a module from my local project  in C style (#include
>> "local.h").
>
> No.
>
>>
>> I know I can do "dmd main.d local.d" but I wonder if it can be done C
>> style.
>
> What is your goal? Why doesn't D import work for you?
>
> -Steve

I organize some exercises in some source files, it's more how I like to work with C. I'm used to organize source files this way and I was wondering if this was possible with D.

Thank you for your response Steven

On 6/25/15 10:37 AM, Binarydepth wrote:
> On Thursday, 25 June 2015 at 14:10:00 UTC, Steven Schveighoffer wrote:
>> On 6/25/15 9:57 AM, Binarydepth wrote:
>>> I want to import a module from my local project  in C style (#include
>>> "local.h").
>>
>> No.
>>
>>>
>>> I know I can do "dmd main.d local.d" but I wonder if it can be done C
>>> style.
>>
>> What is your goal? Why doesn't D import work for you?
>>
>> -Steve
>
> I organize some exercises in some source files, it's more how I like to
> work with C. I'm used to organize source files this way and I was
> wondering if this was possible with D.

Well, if you publicly import the other module, it pulls all those public symbols as if they were defined in the importing module.

Perhaps this would work for you.

-Steve

On Thursday, 25 June 2015 at 14:37:28 UTC, Binarydepth wrote:
>
> I organize some exercises in some source files, it's more how I like to work with C. I'm used to organize source files this way and I was wondering if this was possible with D.
>

If the files are in the same folder, just import local; in the main.d file and then run dmd main.d from the command line. You might need to ensure that there is only one main function.

If the files are in different folders, you have to use a -I to the folder that contains local.d.

I would recommend familiarizing yourself with Dub. It may make your life easier.

On Thursday, 25 June 2015 at 17:20:46 UTC, jmh530 wrote:
> On Thursday, 25 June 2015 at 14:37:28 UTC, Binarydepth wrote:
>>
>> I organize some exercises in some source files, it's more how I like to work with C. I'm used to organize source files this way and I was wondering if this was possible with D.
>>
>
> If the files are in the same folder, just import local; in the main.d file and then run dmd main.d from the command line. You might need to ensure that there is only one main function.
>
> If the files are in different folders, you have to use a -I to the folder that contains local.d.
>
> I would recommend familiarizing yourself with Dub. It may make your life easier.

Made a mistake. I was testing this with rdmd. rdmd main.d works fine because it builds dependencies, but dmd main.d does not work. You need it like you had it before, dmd main.d local.d.

On Thursday, 25 June 2015 at 13:57:35 UTC, Binarydepth wrote:
> I want to import a module from my local project  in C style (#include "local.h").

You can theoretically do this with `mixin(import("local.d"));`. This will more or less copy-paste the content of local.d into the current scope. You also need to pass `-J.` to the compiler to allow it to read the file.

But I would try to make it work with normal imports instead.

On Thursday, 25 June 2015 at 14:10:00 UTC, Steven Schveighoffer wrote:
> On 6/25/15 9:57 AM, Binarydepth wrote:
>> I want to import a module from my local project  in C style (#include
>> "local.h").
>
> No.
>
>>
>> I know I can do "dmd main.d local.d" but I wonder if it can be done C
>> style.
>
> What is your goal? Why doesn't D import work for you?
>
> -Steve

No goal just wondering, Thanks!

In the future when GDC and MAKE can work together I want to just do "make code" and have the non-standard, custom libraries be supplied to the compiler by MAKE.

For a project I would just write the Makefile for this