Incomprehensible compiler errors

[Don Clugston]

On 31/07/12 00:54, Stuart wrote:
> On Monday, 30 July 2012 at 21:40:35 UTC, Walter Bright wrote:
>>
>> A ModuleInfo is generated for each compiled module and inserted into
>> its corresponding .obj file. If the linker cannot find it, then it is
>> likely that you need to specify that .obj on the link command.
>
> Ah, it would seem that my problem is with DFL not compiling. Look guys,
> I'm about ready to give up here. I like the idea of D, but it's like
> using fucking Linux: Absolutely everything needs to be compiled before
> you can use it; and nothing will compile because you need to do fifty
> other goddamn things that aren't mentioned in the readme, so you have to
> post on dozens of sodding forums for a week hoping someone throws you a
> bone.

>
> All I want is to be able to write a GUI application using phrases like
> "button1.dock = Fill". Is that so much to ask? Apparently it is.
>
> DFL won't compile. D-IDE doesn't work at all. VisualD crashes all the
> time. The Eclipse IDE plugin doesn't work either. None of the IDEs have
> any kind of reliable intellisense. The optional "module" keywords aren't
> optional. The whole fucking thing's a shambles, just like everything
> else designed for Linux.
>
> It's really getting on my tits. Even using MFC is easier than this.

Yeah, we still have *miles* to go on the toolchain. As a community we've 
been putting most of our effort into getting the compiler stable, and to 
a lesser extent working on the the standard library. Most of the other 
things are one-man shows.
The Eclipse plugin and DFL have both been abandoned for years.
Mono-D and VisualD are progressing quite well but again they are only 
one-man shows.

We need more people.