"Graham Fawcett" wrote in message
news:ivpgt6$28l3$5...@digitalmars.com...
> On Fri, 15 Jul 2011 00:31:39 +0200, David Nadlinger wrote:
>
>> On 7/15/11 12:29 AM, Trass3r wrote:
It can't:
- build import graphs and do partial rebuilds (waste of time with D)
>>>
>>> dmd, not D! ;)
>>
>> An
On Fri, 15 Jul 2011 00:31:39 +0200, David Nadlinger wrote:
> On 7/15/11 12:29 AM, Trass3r wrote:
>>> It can't:
>>> - build import graphs and do partial rebuilds (waste of time with D)
>>
>> dmd, not D! ;)
>
> And only for smaller projects.
>
> David
Can you clarify why larger projects are bette
Until DMD eats up so much memory it starts to crawl down and become
slow, at which point single object builds are much faster. They are on
my system at least.
On Thu, Jul 14, 2011 at 5:06 PM, Martin Nowak wrote:
> Well in D the semantics of a module are independent of where it is imported
> from.
> So you can parse/analyze a module once and reuse that information, while
> with single object builds you'll have to redo this work for each import.
>
>
Yes,
Well in D the semantics of a module are independent of where it is
imported from.
So you can parse/analyze a module once and reuse that information, while
with single object builds you'll have to redo this work for each import.
On Fri, 15 Jul 2011 00:29:02 +0200, Trass3r wrote:
It can't:
On 7/15/11 12:29 AM, Trass3r wrote:
It can't:
- build import graphs and do partial rebuilds (waste of time with D)
dmd, not D! ;)
And only for smaller projects.
David
It can't:
- build import graphs and do partial rebuilds (waste of time with D)
dmd, not D! ;)
Because the discussion is rising up, I just added some help/information to
a small tool I wrote some month ago.
It's raison d'être was the ability to develop a larger project out of
smaller libraries.
It can:
- compactly specify build targets
- install packages with imports/documentation
-
