There is a bug tracker for the D front end for GCC on the dgcc Sourceforge project page, but it is apparently not in use.  It took me a little while to find the right place to report bugs.  Has anyone considered taking down the Sourceforge ticket system and having it link to the bug tracker that the D project really uses?

Leo Singer wrote:
> There is a bug tracker for the D front end for GCC on the dgcc
> Sourceforge project page, but it is apparently not in use.  It took
> me a little while to find the right place to report bugs.  Has anyone
> considered taking down the Sourceforge ticket system and having it
> link to the bug tracker that the D project really uses?

Sounds like a good idea, but needs to be done by the project maintainer.

--anders

Anders F Björklund Wrote:

> Leo Singer wrote:
> > There is a bug tracker for the D front end for GCC on the dgcc Sourceforge project page, but it is apparently not in use.  It took me a little while to find the right place to report bugs.  Has anyone considered taking down the Sourceforge ticket system and having it link to the bug tracker that the D project really uses?
> 
> Sounds like a good idea, but needs to be done by the project maintainer.
> 
> --anders

I'm a little confused about who maintains the D front end and who maintains GDC.  I've submitted bug reports on Digital Mars' bug tracker, but they are bugs related to GDC.  I've submitted bug reports on GDC's tracker as well, but they go unanswered.  It would be really nice if the Digital Mars pages made the status of GDC vs. DCC more clear.

I've been using D for a few weeks, and the one thing I'll say is that it's made programming fun again.  I'm writing some embedded signal processing software for an underwater sonar system.  I'd really like to do the embedded programming in D.


But the