On 5/5/2022 11:18 PM, Patrick Schluter wrote:
> That's the point. It reduces build complexity in a disruptive way.

As someone who used to write C code to generate C code to be compiled into a program, this was all replaced very nicely with CTFE. CTFE is worth it just for that. I sure enjoyed deleting all that stuff. Good riddance.

(The multi-level build process broke many "better make" replacements.)

On 5/5/2022 11:57 PM, Siarhei Siamashka wrote:
> My point is that CTFE actually increases the complexity and moves it somewhere else in a somewhat obscure way. It's one of the zillions of extra features that make the language spec bloated and difficult to learn.

Actually, it doesn't add any new syntax. And it removes that peculiar limitation that functions cannot be used to determine enum values. It's more the removal of a compiler limitation than adding a feature.

CTFE in C++ was a new feature, as it (pointlessly) added new syntax with new rules.

On 5/6/2022 10:30 AM, Adam D Ruppe wrote:
> http://dpldocs.info/this-week-in-d/Blog.Posted_2022_05_02.html


You wrote about new D bug-detecting features not finding bugs in existing code.

This is completely unsurprising. For example, I ran one of those new C++ bug finding scanners over DMD (back when it was still in C++). How many bugs did it find? Zero.

The thing is, the DMD source code was very well tested. The routine coding bugs that caused problems were already fixed.

The bug finding features are for *new* code, so you can find the bugs at compile time when it is much more efficient to fix them.

On 5/6/2022 12:26 AM, Araq wrote:
> It was in the Nim(rod) compiler which is a Modula 3 derivate quite early in the project's lifetime, maybe as early as 2004, maybe later, I don't remember. And maybe D had it earlier. However:
> 
> 1. I'm quite sure I didn't copy it from D. Because:
> 2. Nim actually **needs** it because otherwise its AST macro system simply cannot work.
> 

You wrote the Nimrod compiler? I'm impressed!

On 5/6/2022 11:59 AM, tastyminerals wrote:
> And I would love D to just `import awesomeClib;`.

That's very much what ImportC is all about.

On Fri, May 06, 2022 at 08:10:16PM -0700, Walter Bright via Digitalmars-d wrote: [...]
> (The multi-level build process broke many "better make" replacements.)

IMNSHO, "better make" replacements that cannot handle multi-level builds are not worthy to be considered as "better make", but "worse make". (Including, unfortunately, dub. I've been thinking about how to break dub out of its walled garden, partly to remove this limitation.)


T

-- 
Political correctness: socially-sanctioned hypocrisy.