Thanks everyone.
So, the upshot of it all seems to be that the -i's have it.
On Fri, Dec 07, 2018 at 07:01:18PM +, Adam D. Ruppe via Digitalmars-d-learn
wrote:
> On Friday, 7 December 2018 at 17:41:47 UTC, Ron Tarrant wrote:
[...]
> > when I compile rather than compiling modules over and over
> > needlessly.
>
> Oh, lots of us compile everything at once. It works
On Friday, 7 December 2018 at 17:41:47 UTC, Ron Tarrant wrote:
Are you talking about a list of import statements here or is
there another way/place I would list them?
On the dmd command line. So say your program has a.d and b.d, you
would compile with `dmd a.d b.d`.
Or as you had some
On Sat, Dec 08, 2018 at 06:48:46AM +1300, rikki cattermole via
Digitalmars-d-learn wrote:
> On 08/12/2018 6:41 AM, Ron Tarrant wrote:
> > Does D have the concept of makefiles? I haven't run across any
> > reference to such things so far.
>
> Make isn't a D specification application (it doesn't
On 08/12/2018 6:41 AM, Ron Tarrant wrote:
Does D have the concept of makefiles? I haven't run across any reference
to such things so far.
Make isn't a D specification application (it doesn't really specialize
in any language) dmd, druntime and Phobos are all built using it.
Though for user
On Friday, 7 December 2018 at 16:43:02 UTC, Adam D. Ruppe wrote:
That's wrong: the import name and the module name should always
match, in full, including all the dot parts.
So if you "import app.modulename;", the other file must have
"module app.modulename;"
Okay. I guess the instructions
On Friday, 7 December 2018 at 16:39:34 UTC, Ron Tarrant wrote:
import subfolder.ModuleName;
And in the module files, the first statement is:
module ModuleName;
That's wrong: the import name and the module name should always
match, in full, including all the dot parts.
So if you "import
