Jascha Wetzel wrote:
> Thomas Brix Larsen wrote:
>> Jascha Wetzel wrote:
>>> Thomas Brix Larsen wrote:
>>>> vanh wrote:
>>>>
>>>>> Could you make it work with Ddbg? That would be cool!
>>>>>
>>>>> vtp
>>>>>
>>>> Seeing as Ddbg is Windows-only, that won't happen.
>>>>
>>>> Though I'll probally add support for some crossplatform debugger in the future.
>>>>
>>>> - Brix
>>>>
>>> by adding GDB CLI support, you effectively add cross platform debugging and also integrate Ddbg
>>>
>> 
>> So Ddbg will give the same output as GDB if supplied with a GDB command?
>> 
>> What about support for GDB/MI?
>> 
>> - Brix
>>
> if Ddbg's filename contains "gdb", it switches to GDB emulation. it
> mimics the GDB CLI just enough such that Code::Blocks is happy with it.
> unfortunately C::B doesn't use GDB/MI.
> if there is enough demand for it, i'll make sure Ddbg's emulation works
> with other GUIs as well (e.g. add GDB/MI if necessary). i'd like to keep
> the number of different CLIs as small as possible, though, since they
> all need to be maintained.
> 

It's understandable that you desire to have as little maintenance work as possible. ;)

I guess you don't have a Unix port planned for Ddbg?

- Brix

Thomas Brix Larsen wrote:
> I guess you don't have a Unix port planned for Ddbg?

right now, the windows specific code (win32+codeview) in Ddbg takes up about 40%. that makes a port a pretty big task. i'll do that when the win32 version has little left to be desired and there still is no D debugger for linux (which is very unlikely, though).

It seems that the doc generation maps the module name to the target html file. This causes problems at least with Tango's documentation. I just found out that the tango.math.Core module's documentation is overwritten by tango.text.locale.Core documentation, as they have the same module name. Maybe you could add the package part to the file name?

O.

Olli Aalto wrote:

> It seems that the doc generation maps the module name to the target html file. This causes problems at least with Tango's documentation. I just found out that the tango.math.Core module's documentation is overwritten by tango.text.locale.Core documentation, as they have the same module name. Maybe you could add the package part to the file name?
> 
> O.

Yeah, I had a feeling that might happen.

I guess I'll have to write a wrapper for doc generation. I'll release some updated documentation as soon as possible.

- Brix

Olli Aalto wrote:
> It seems that the doc generation maps the module name to the target html file. This causes problems at least with Tango's documentation. I just found out that the tango.math.Core module's documentation is overwritten by tango.text.locale.Core documentation, as they have the same module name. Maybe you could add the package part to the file name?
> 
> O.

I do not find this to be the case.  Do your URL's match up with these?

http://www.dsource.org/projects/tango/docs/current/tango.math.Core.html

http://www.dsource.org/projects/tango/docs/current/tango.text.locale.Core.html

For me they show up as two distinct pages and appear to be correct.  Are you talking about your local machine?

Cheers,
BA

Brad Anderson wrote:
> Olli Aalto wrote:
>> It seems that the doc generation maps the module name to the target html file. This causes problems at least with Tango's documentation. I just found out that the tango.math.Core module's documentation is overwritten by tango.text.locale.Core documentation, as they have the same module name. Maybe you could add the package part to the file name?
>>
>> O.
> 
> I do not find this to be the case.  Do your URL's match up with these?
> 
> http://www.dsource.org/projects/tango/docs/current/tango.math.Core.html
> 
> http://www.dsource.org/projects/tango/docs/current/tango.text.locale.Core.html
> 
> For me they show up as two distinct pages and appear to be correct.  Are you talking about your local machine?
> 
> Cheers,
> BA

Sorry for the noise.  Thomas answered in the other fork of this thread.

BA

Here is the promised "docfix" release for eDitor.

Changes (0.42 to 0.43)

Bugfixes:
   * Tango documentation had file conflicts and has been updated.

Get it here: http://brix-verden.dk/d/editor.html

Or get the updated docs here: http://brix-verden.dk/d/eDitor/eDitor-0.43-docs.tar.bz2

The updated docs is for people who already have eDitor 0.42.

Enjoy! ;)

- Brix

update: GDB/MI is definitely going to come. probably not in the next release, but soon thereafter...

Thomas Brix Larsen wrote:
> Jascha Wetzel wrote:
>> Thomas Brix Larsen wrote:
>>> vanh wrote:
>>>
>>>> Could you make it work with Ddbg? That would be cool!
>>>>
>>>> vtp
>>>>
>>> Seeing as Ddbg is Windows-only, that won't happen.
>>>
>>> Though I'll probally add support for some crossplatform debugger in the future.
>>>
>>> - Brix
>>>
>> by adding GDB CLI support, you effectively add cross platform debugging and also integrate Ddbg
>>
> 
> So Ddbg will give the same output as GDB if supplied with a GDB command?
> 
> What about support for GDB/MI?
> 
> - Brix
>