On Tuesday, 19 November 2013 at 13:15:43 UTC, Bruno Medeiros wrote:
>> Yes, manual setup is possible, but you must use absolute path without `~`.
>
> Exactly, although you can use some Eclipse resource variables in the path of linked folders.

Do you have any plans to improve this situation? For example, we can add a bug report that Eclipse doesn't support relative paths.

On 2013-11-19 14:17, Bruno Medeiros wrote:

> Nah, the interface that GDB frontends use is an API for backends only
> called MI (Machine Interface). It's different from the console
> interpreter, and LLDB does not support that:
> http://lists.cs.uiuc.edu/pipermail/lldb-dev/2013-February/001456.html

Ok, I see.

-- 
/Jacob Carlborg

On 19/11/2013 13:29, ilya-stromberg wrote:
> On Tuesday, 19 November 2013 at 13:15:43 UTC, Bruno Medeiros wrote:
>>> Yes, manual setup is possible, but you must use absolute path without
>>> `~`.
>>
>> Exactly, although you can use some Eclipse resource variables in the
>> path of linked folders.
>
> Do you have any plans to improve this situation? For example, we can add
> a bug report that Eclipse doesn't support relative paths.

You can add that bug report yourself to Eclipse, that's pretty much independent of DDT. Personally I don't find it to be a significant limitation at all.
Note that you can create an Eclipse resource variable to point to HOME, and then create linked folders relative to that variable. For example you could then link an Eclipse folder to "HOME/.dub/packages"

-- 
Bruno Medeiros - Software Engineer

On 18/11/2013 20:51, Iain Buclaw wrote:
> On 18 November 2013 15:49, Bruno Medeiros <brunodomedeiros+dng@gmail.com
> <mailto:brunodomedeiros+dng@gmail.com>> wrote:
>
>     On 14/11/2013 17:54, Bruno Medeiros wrote:
>
>         DDT 0.9.0 ("Debugging is Magic") is out, see post:
>         https://groups.google.com/d/__msg/ddt-ide/VwA7ifYt9c0/__wBcvUSVKNqMJ
>         <https://groups.google.com/d/msg/ddt-ide/VwA7ifYt9c0/wBcvUSVKNqMJ>
>
>
>     BTW, the CDT devs are contemplating supporting LLDB as well:
>     https://bugs.eclipse.org/bugs/__show_bug.cgi?id=405670
>     <https://bugs.eclipse.org/bugs/show_bug.cgi?id=405670>
>     (primarily motivated by the poor support for GDB toolchain in Mac)
>
>     Nothing is decided or started yet, but it would be quite nice if
>     they went for it, as then LLDB support could be trivially added to
>     DDT as well. *fingers crossed*
>     Especially cool since the LDC compiler seems to be keeping up with
>     DMD and being up to date better than GDC (this is just my
>     impression, I haven't checked this claim)
>
>
> Check you claims. :o)
>
>
> The only discrepancy as of writing is that Martin's work on shared
> library support is incompatible with, and currently blocking the 2.064
> merge in GDC.
>
>
> --
> Iain Buclaw
>
> *(p < e ? p++ : p) = (c & 0x0f) + '0';

That claim is based on the observation that the latest GDC binary distributable for Windows (which even so is not quite official and of unknown stability) is based on DMD 2.060 whereas LDC has binary releases based on 2.063.2 ...

Sure, the GDC development source maybe be more up to date to DMD, but:
a) I have no idea how stable that is. Are there even releases?
b) I find that the official GDC installation instructions for Windows (http://www.gdcproject.org/wiki/MinGW) are way overkill, much more hassle than should be required to install GDC.

-- 
Bruno Medeiros - Software Engineer

On Tuesday, 19 November 2013 at 13:15:43 UTC, Bruno Medeiros wrote:
> On 18/11/2013 15:32, ilya-stromberg wrote:
>> On Monday, 18 November 2013 at 15:28:36 UTC, Jacek Furmankiewicz wrote:
>>> Quick question: with the current version is it possible to use it with
>>> a dub project at all (maybe via a manual project setup)?
>>>
>>> I was trying to manually set it up, pointing "sources" as the source
>>> folder and trying to get the ~/.dub/packages into the list of
>>> libraries, but it did not seem to like it...
>>
>> Yes, manual setup is possible, but you must use absolute path without `~`.
>
> Exactly, although you can use some Eclipse resource variables in the path of linked folders.

why this?

https://github.com/bruno-medeiros/DDT/commit/b7a57f9e0d7915734ba6b175acfc1fd53a7a92f4

On 02/12/2013 10:35, eles wrote:
> On Tuesday, 19 November 2013 at 13:15:43 UTC, Bruno Medeiros wrote:
>> On 18/11/2013 15:32, ilya-stromberg wrote:
>>> On Monday, 18 November 2013 at 15:28:36 UTC, Jacek Furmankiewicz wrote:
>>>> Quick question: with the current version is it possible to use it with
>>>> a dub project at all (maybe via a manual project setup)?
>>>>
>>>> I was trying to manually set it up, pointing "sources" as the source
>>>> folder and trying to get the ~/.dub/packages into the list of
>>>> libraries, but it did not seem to like it...
>>>
>>> Yes, manual setup is possible, but you must use absolute path without
>>> `~`.
>>
>> Exactly, although you can use some Eclipse resource variables in the
>> path of linked folders.
>
> why this?
>
> https://github.com/bruno-medeiros/DDT/commit/b7a57f9e0d7915734ba6b175acfc1fd53a7a92f4
>

The commit it reverted was not meant to go to master, but to a branch. The idea is that master is to be kept potentially shipable at all times, and dub support is not ready (nor was it disabled in the original commit, which is another way that it could be allowed to be commited to master).

-- 
Bruno Medeiros - Software Engineer

On Thursday, 21 November 2013 at 13:56:38 UTC, Bruno Medeiros wrote:
> That claim is based on the observation that the latest GDC binary distributable for Windows (which even so is not quite official and of unknown stability) is based on DMD 2.060 whereas LDC has binary releases based on 2.063.2 ...

Finally somebody who appreciates our efforts. ;)

David

On Monday, 2 December 2013 at 15:55:22 UTC, Bruno Medeiros wrote:
> On 02/12/2013 10:35, eles wrote:
>> On Tuesday, 19 November 2013 at 13:15:43 UTC, Bruno Medeiros wrote:
>>> On 18/11/2013 15:32, ilya-stromberg wrote:
>>>> On Monday, 18 November 2013 at 15:28:36 UTC, Jacek Furmankiewicz wrote:

> The commit it reverted was not meant to go to master, but to a branch. The idea is that master is to be kept potentially shipable at all times, and dub support is not ready (nor was it disabled in the original commit, which is another way that it could be allowed to be commited to master).

Uf! I thought that you dropped the idea of dub support. Glad to hear that you did not.

Nice. Always keeping master bug fix complete with all completed features make people more likely to use tip.   Another related method of managing versions that I've seen is to create forks when you want to do a release. On 2 Dec 2013 18:00, "Bruno Medeiros" <brunodomedeiros+dng@gmail.com> wrote:

> On 02/12/2013 10:35, eles wrote:
>
>> On Tuesday, 19 November 2013 at 13:15:43 UTC, Bruno Medeiros wrote:
>>
>>> On 18/11/2013 15:32, ilya-stromberg wrote:
>>>
>>>> On Monday, 18 November 2013 at 15:28:36 UTC, Jacek Furmankiewicz wrote:
>>>>
>>>>> Quick question: with the current version is it possible to use it with a dub project at all (maybe via a manual project setup)?
>>>>>
>>>>> I was trying to manually set it up, pointing "sources" as the source folder and trying to get the ~/.dub/packages into the list of libraries, but it did not seem to like it...
>>>>>
>>>>
>>>> Yes, manual setup is possible, but you must use absolute path without `~`.
>>>>
>>>
>>> Exactly, although you can use some Eclipse resource variables in the path of linked folders.
>>>
>>
>> why this?
>>
>> https://github.com/bruno-medeiros/DDT/commit/ b7a57f9e0d7915734ba6b175acfc1fd53a7a92f4
>>
>>
> The commit it reverted was not meant to go to master, but to a branch. The idea is that master is to be kept potentially shipable at all times, and dub support is not ready (nor was it disabled in the original commit, which is another way that it could be allowed to be commited to master).
>
> --
> Bruno Medeiros - Software Engineer
>

Hi Bruno,

First off, I wanted to share my appreciation for working on D support in Eclipse and especially for introducing the debugging capabilities with DDT - really awesome!

I started playing around with the CDT debugger for D programs and so far got a question about D dynamic arrays.
Actually they're already supported by GDB "out of box", and indeed debugging with GDB 7.6.2 allows for the following array's output:

<code line> int[] a = [7, 5];

(gdb) print a
$1 = {7, 5}

but still, if debugging the same code in Eclipse (CDT), I see:
a	struct _Array_int	{...}	
  length	unsigned long	2	
  ptr	int *	0x7ffff7ecdfd0	

While it is definitely possible to implement some custom pretty printers for this (and it shouldn't be that hard), I wanted to first ask whether you have some clue about how can the D-style array output be forced in CDT. Thanks!