There is a new IDE call codeblock that seems to support D compiler. http://www.codeblocks.org/

vtp

vtp Wrote:

> There is a new IDE call codeblock that seems to support D compiler. http://www.codeblocks.org/
> 
> vtp

Code::Blocks has been around for quite a while. Have you tried its D support? I'm curious to know whether it's any good...

Whilst I'm all for ubiquitous support for D (and without having used Code::Blocks for D), I think that Poseidon and the Descent project will both dwarf whatever support Code::Blocks has for D, and be more suitable overall (given that Code::Blocks is very much focussed on C++).

What I would love to see, on the other hand, is D support in KDevelop. If nobody's working on it, I might have to make that one of my personal projects for this year. :)

vtp Wrote:

> There is a new IDE call codeblock that seems to support D compiler. http://www.codeblocks.org/
> 
> vtp

You have to use the nightly build of Code::Blocks to get D support.  Currently it only has one D wizard that creates a D application.  I've been using it with GDC and it ain't bad.  But what it really lacks is code completion for D.  It also works with the Digital Mars compiler too if thats your preferred D tool.

Stan Brown Wrote:

> vtp Wrote:
> 
> > There is a new IDE call codeblock that seems to support D compiler. http://www.codeblocks.org/
> > 
> > vtp
> 
> You have to use the nightly build of Code::Blocks to get D support.  Currently it only has one D wizard that creates a D application.  I've been using it with GDC and it ain't bad.  But what it really lacks is code completion for D.  It also works with the Digital Mars compiler too if thats your preferred D tool.


Well, that what I'm using together with dmd 1.0 compiler seems to work fine, except that gdb 6.6 doesn't work, or I just don't know how to set it up to debug D.

vtp

just jeff wrote:

> Code::Blocks has been around for quite a while. Have you tried its D
> support? I'm curious to know whether it's any good...

Code::Blocks currently supports D as a "C/C++ compiler", that is it
thinks that DMD or GDC is some weird compiler with strange flags...
Support for D "proper" and support for Mac OS X has been pushed to
past the 1.0 release, in other to not delay that for another year.

That doesn't mean that you can't use D (or Mac) now, because you can.

> Whilst I'm all for ubiquitous support for D (and without having used
> Code::Blocks for D), I think that Poseidon and the Descent project
> will both dwarf whatever support Code::Blocks has for D, and be more
> suitable overall (given that Code::Blocks is very much focussed on
> C++).

The "native" D projects will probably be better (even ported from Java),
the advantage of using old C++ solutions like wxWidgets / Code::Blocks
is that you can use that bigger old code base and community for help...
And this is why the IDE projects for wxD 1.0 will be Code::Blocks 1.0.

http://wxd.sourceforge.net/#codeblocks

--anders

Stan Brown wrote:

> You have to use the nightly build of Code::Blocks to get D support.
> Currently it only has one D wizard that creates a D application.

The wizards could use some love, as they're still using previous D:

int main(char[][] args)
{
    printf("hello world\n");
    printf("args.length = %d\n", args.length);
    for (int i = 0; i < args.length; i++)
        printf("args[%d] = '%s'\n", i, cast(char *)args[i]);
    return 0;
}

Converting that over to writef and foreach would probably be nice ?

import std.stdio;

void main(char[][] args)
{
    writefln("hello world");
    writefln("args.length = ", args.length);
    foreach(int i, char[] arg; args)
        writefln("args[%d]", i, " = '%s'", arg);
}

Even better would be if printf could just go back to std.c.stdio...

--anders

Anders F Björklund wrote:
> Code::Blocks currently supports D as a "C/C++ compiler", that is it thinks that DMD or GDC is some weird compiler with strange flags... Support for D "proper" and support for Mac OS X has been pushed to past the 1.0 release, in other to not delay that for another year.
>
> That doesn't mean that you can't use D (or Mac) now, because you can.

Maybe even more notably, CodeBlocks supports "find implementation of"
and "goto function" for D files. This is probably just because the
edit-time C++ parser inherently understands parts of D.
I actually don't miss too much from my MSDEV+VisualAssistX or Eclipse
for Java setup, except for the refactoring tools.

just jeff kirjoitti:
> What I would love to see, on the other hand, is D support in KDevelop. If nobody's working on it, I might have to make that one of my personal projects for this year. :)

I would also like it. I don't know how much work does it take now. I've been using Kate for D projects and it seems to have quite good support for the D syntax. Isn't the text editor in KDevelop using the same widget?

Jari-Matti Mäkelä wrote:
> just jeff kirjoitti:
>> What I would love to see, on the other hand, is D support in KDevelop. If nobody's working on it, I might have to make that one of my personal projects for this year. :)
> 
> I would also like it. I don't know how much work does it take now. I've
> been using Kate for D projects and it seems to have quite good support
> for the D syntax. Isn't the text editor in KDevelop using the same widget?

That is convenient, but I'm also looking for D-aware features such as:

- DDoc popping up where appropriate (similar to the way NetBeans/Eclipse do it for Javadoc
- GDB integration
- "Jump to definition" and friends
- Interpretation of compiler errors (e.g. ability to jump to the line that caused the error)

Someone should hack apart the tutorial files/wizard and update it and resubmit to
CodeBlocks...
I haven't been using CB for long enough to feel comfortable, but Yes, the switch
over would be nice.
-gcs