Something for the weekend:

A new version of DDT - D Development Tools is out.
Some minor improvements and some important fixes. Please take the time to read the Changelog:

http://code.google.com/p/ddt/wiki/ChangeLog#DDT_0.8.0_%282013-08-30%29

-- 
Bruno Medeiros - Software Engineer

On Friday, 30 August 2013 at 17:46:19 UTC, Bruno Medeiros wrote:
> Something for the weekend:
>
> A new version of DDT - D Development Tools is out.
> Some minor improvements and some important fixes. Please take the time to read the Changelog:
>
> http://code.google.com/p/ddt/wiki/ChangeLog#DDT_0.8.0_%282013-08-30%29

> Updated DDT to latest version of DLTK (version 5.0, from Eclipse Kepler).

Does DLTK (Dynamic Languages Toolkit) 3.0 still supported?

On 02/09/2013 10:49, ilya-stromberg wrote:
> On Friday, 30 August 2013 at 17:46:19 UTC, Bruno Medeiros wrote:
>> Something for the weekend:
>>
>> A new version of DDT - D Development Tools is out.
>> Some minor improvements and some important fixes. Please take the time
>> to read the Changelog:
>>
>> http://code.google.com/p/ddt/wiki/ChangeLog#DDT_0.8.0_%282013-08-30%29
>
>> Updated DDT to latest version of DLTK (version 5.0, from Eclipse Kepler).
>
> Does DLTK (Dynamic Languages Toolkit) 3.0 still supported?

No, it has to be the latest one only, 5.0 .

-- 
Bruno Medeiros - Software Engineer

On Monday, 2 September 2013 at 10:42:41 UTC, Bruno Medeiros wrote:
> On 02/09/2013 10:49, ilya-stromberg wrote:
>> On Friday, 30 August 2013 at 17:46:19 UTC, Bruno Medeiros wrote:
>
> No, it has to be the latest one only, 5.0 .

What prevents integration with the gdb and Eclipse debug interface?

On 02/09/2013 12:38, eles wrote:
> On Monday, 2 September 2013 at 10:42:41 UTC, Bruno Medeiros wrote:
>> On 02/09/2013 10:49, ilya-stromberg wrote:
>>> On Friday, 30 August 2013 at 17:46:19 UTC, Bruno Medeiros wrote:
>>
>> No, it has to be the latest one only, 5.0 .
>
> What prevents integration with the gdb and Eclipse debug interface?

Nothing, it is just a task no one has approached yet.
I'm the only developer contributing so far, and I've been tied up with other more tasks I considered more prioritary. (the new parser, updating to latest Eclipse/DLTK release, etc.)

There is a few improvements I want to make to the Code Completion engine, after that I should go to tackle debugger integration.

-- 
Bruno Medeiros - Software Engineer

On 9/2/13 2:02 PM, Bruno Medeiros wrote:
> On 02/09/2013 12:38, eles wrote:
>> On Monday, 2 September 2013 at 10:42:41 UTC, Bruno Medeiros wrote:
>>> On 02/09/2013 10:49, ilya-stromberg wrote:
>>>> On Friday, 30 August 2013 at 17:46:19 UTC, Bruno Medeiros wrote:
>>>
>>> No, it has to be the latest one only, 5.0 .
>>
>> What prevents integration with the gdb and Eclipse debug interface?
>
> Nothing, it is just a task no one has approached yet.
> I'm the only developer contributing so far, and I've been tied up with
> other more tasks I considered more prioritary. (the new parser, updating
> to latest Eclipse/DLTK release, etc.)
>
> There is a few improvements I want to make to the Code Completion
> engine, after that I should go to tackle debugger integration.
>

Did you consider reusing some code from Descent for the debugger? I remember it was one part of the project that was separte from other parts and it worked quite well.

On 02/09/2013 23:00, Ary Borenszweig wrote:
> On 9/2/13 2:02 PM, Bruno Medeiros wrote:
>> On 02/09/2013 12:38, eles wrote:
>>> On Monday, 2 September 2013 at 10:42:41 UTC, Bruno Medeiros wrote:
>>>> On 02/09/2013 10:49, ilya-stromberg wrote:
>>>>> On Friday, 30 August 2013 at 17:46:19 UTC, Bruno Medeiros wrote:
>>>>
>>>> No, it has to be the latest one only, 5.0 .
>>>
>>> What prevents integration with the gdb and Eclipse debug interface?
>>
>> Nothing, it is just a task no one has approached yet.
>> I'm the only developer contributing so far, and I've been tied up with
>> other more tasks I considered more prioritary. (the new parser, updating
>> to latest Eclipse/DLTK release, etc.)
>>
>> There is a few improvements I want to make to the Code Completion
>> engine, after that I should go to tackle debugger integration.
>>
>
> Did you consider reusing some code from Descent for the debugger? I
> remember it was one part of the project that was separte from other
> parts and it worked quite well.

I did consider that, but I haven't had the time yet to look into any of the debugger functionality. (and I don't want to just blindly copy the code without at least understanding and testing it sufficiently - and that takes time...)

-- 
Bruno Medeiros - Software Engineer