Incomplete types question

[NoUseForAName via Digitalmars-d-learn]

On Tuesday, 8 July 2014 at 06:28:51 UTC, Ali Çehreli wrote:
> On 07/07/2014 09:44 PM, NoUseForAName wrote:
>> [snip]
[snip]
> 3) Compile the implementation as a library (just a .o in this 
> case):

Thanks.. but this is awkward. I expected there to be keywords to 
declare type declarations public or private. Also using a 
separate .di file means I lose the whole advantage of not having 
to use header files. My idea here was basically to use D as a 
"better C", you know without the annoying stuff like header files 
/ no real modules. Seems C is actually superior for what I want 
to do. .di vs. h is no real advantage, and in C I do not need to 
move the implementation into a library to stop other modules from 
using the type directly.

Again, thanks for the detailed explanation but I guess I am going 
to stick with C for this.