On Wednesday, 13 August 2014 at 21:29:01 UTC, Damian Day wrote:
> On Wednesday, 13 August 2014 at 14:16:18 UTC, Alex wrote:
>> Hey everyone,
>>
>> it's been quite some while ago that I posted a Mono-D release announcement on to D.announce :)
>>
>> You should've noticed that the installation instruction stuff has been moved to
>> the D wiki - http://wiki.dlang.org/Mono-D
>>
>> There have been several fixes and smaller improvements since the last bunch of bug fix releases.
>> Detailed release notes can be taken from the wiki entry.
>>
>>
>>
>> Cheers,
>> Alex
>
> Have you considered integrating some of Brian Schotts work?
> Perhaps an option to pick an engine DCD or DParser.

I'm not sure you'd want to do that. The DParser completion engine has a few features that DCD doesn't have. (I'm not sure if this is true the other way around)

> I'm particularly interested in dscanner integration myself :)

Are you talking about displaying static analysis hints in the editor window, or something else?

On Wednesday, 13 August 2014 at 21:35:26 UTC, Brian Schott wrote:
> I'm not sure you'd want to do that. The DParser completion engine has a few features that DCD doesn't have. (I'm not sure if this is true the other way around)
>
>> I'm particularly interested in dscanner integration myself :)
>
> Are you talking about displaying static analysis hints in the editor window, or something else?

It would be nice if we could have one unified auto complete engine instead of several different engines of varying quality and feature sets. But it is only a dream.

On Wednesday, 13 August 2014 at 21:48:57 UTC, Tofu Ninja wrote:
> It would be nice if we could have one unified auto complete engine instead of several different engines of varying quality and feature sets. But it is only a dream.

For that matter... it would be nice to have just one unified
parser.....

On Wednesday, 13 August 2014 at 21:35:26 UTC, Brian Schott wrote:
> On Wednesday, 13 August 2014 at 21:29:01 UTC, Damian Day wrote:
>> On Wednesday, 13 August 2014 at 14:16:18 UTC, Alex wrote:
>>> Hey everyone,
>>>
>>> it's been quite some while ago that I posted a Mono-D release announcement on to D.announce :)
>>>
>>> You should've noticed that the installation instruction stuff has been moved to
>>> the D wiki - http://wiki.dlang.org/Mono-D
>>>
>>> There have been several fixes and smaller improvements since the last bunch of bug fix releases.
>>> Detailed release notes can be taken from the wiki entry.
>>>
>>>
>>>
>>> Cheers,
>>> Alex
>>
>> Have you considered integrating some of Brian Schotts work?
>> Perhaps an option to pick an engine DCD or DParser.
>
> I'm not sure you'd want to do that. The DParser completion engine has a few features that DCD doesn't have. (I'm not sure if this is true the other way around)

That's true, but duplicated work and all that.. It would be a nice way to battle test DCD and the lexer.

>> I'm particularly interested in dscanner integration myself :)
>
> Are you talking about displaying static analysis hints in the editor window, or something else?

Yes precisely.

On Thursday, 14 August 2014 at 00:43:38 UTC, Damian Day wrote:
>> I'm not sure you'd want to do that. The DParser completion engine has a few features that DCD doesn't have. (I'm not sure if this is true the other way around)
>
> That's true, but duplicated work and all that.. It would be a nice way to battle test DCD and the lexer.

Keep in mind that integrating a lexer/parser written in C# into an IDE written in C# is much easier than integrating libdparse would be. The same argument applies to Eclipse and Visual Studio.

>>> I'm particularly interested in dscanner integration myself :)
>>
>> Are you talking about displaying static analysis hints in the editor window, or something else?
>
> Yes precisely.

This should be easy. I have Textadept set up to do this and the implementation is only a few lines long.

https://github.com/Hackerpilot/TextadeptModules/blob/master/modules/dmd/init.lua#L29-54

On Wednesday, 13 August 2014 at 21:29:01 UTC, Damian Day wrote:
> On Wednesday, 13 August 2014 at 14:16:18 UTC, Alex wrote:
>> Hey everyone,
>>
>> it's been quite some while ago that I posted a Mono-D release announcement on to D.announce :)
>>
>> You should've noticed that the installation instruction stuff has been moved to
>> the D wiki - http://wiki.dlang.org/Mono-D
>>
>> There have been several fixes and smaller improvements since the last bunch of bug fix releases.
>> Detailed release notes can be taken from the wiki entry.
>>
>>
>>
>> Cheers,
>> Alex
>
> Have you considered integrating some of Brian Schotts work?
> Perhaps an option to pick an engine DCD or DParser.
> I'm particularly interested in dscanner integration myself :)

In theory, it should be possible if the IPC between the dcd client&server is not too tricky to handle (or is it indeed just a command call? -- But then I had to save a file first to be able to get completion for nearly each keystroke..ugh).

On Thursday, 14 August 2014 at 00:54:07 UTC, Brian Schott wrote:
> On Thursday, 14 August 2014 at 00:43:38 UTC, Damian Day wrote:
>>> I'm not sure you'd want to do that. The DParser completion engine has a few features that DCD doesn't have. (I'm not sure if this is true the other way around)
>>
>> That's true, but duplicated work and all that.. It would be a nice way to battle test DCD and the lexer.
>
> Keep in mind that integrating a lexer/parser written in C# into an IDE written in C# is much easier than integrating libdparse would be. The same argument applies to Eclipse and Visual Studio.

Invoking stuff is easy. I'd rather reimplement the communication to the dcd server instead to not get such a bottleneck if you're on windows or typing really fast. Executing an entire program for each keystroke is a real unsustainable solution, imho.

>
>>>> I'm particularly interested in dscanner integration myself :)
>>>
>>> Are you talking about displaying static analysis hints in the editor window, or something else?
>>
>> Yes precisely.
>
> This should be easy. I have Textadept set up to do this and the implementation is only a few lines long.
>
> https://github.com/Hackerpilot/TextadeptModules/blob/master/modules/dmd/init.lua#L29-54

This seems rather easy to implement.

On Thursday, 14 August 2014 at 07:07:59 UTC, Alex wrote:
> Invoking stuff is easy. I'd rather reimplement the communication to the dcd server instead to not get such a bottleneck if you're on windows or typing really fast. Executing an entire program for each keystroke is a real unsustainable solution, imho.

https://github.com/Hackerpilot/DCD/blob/master/client.d#L72

Alright. :-)

On Thursday, 14 August 2014 at 07:51:11 UTC, Alex wrote:
> On Thursday, 14 August 2014 at 07:07:59 UTC, Alex wrote:
>> Invoking stuff is easy. I'd rather reimplement the communication to the dcd server instead to not get such a bottleneck if you're on windows or typing really fast. Executing an entire program for each keystroke is a real unsustainable solution, imho.
>
> https://github.com/Hackerpilot/DCD/blob/master/client.d#L72
>
> Alright. :-)

Actually, someone has turned on the _"Enable Mixin & Template
Mixin Analysis"_ options?
Major drawbacks?

Someone has turned _off_ the _"Only indent code lines instead of
rearrange code parts"_?
Major drawbacks?

Bye,
dlangophile

On Saturday, 23 August 2014 at 13:19:18 UTC, dlangophile wrote:
> On Thursday, 14 August 2014 at 07:51:11 UTC, Alex wrote:
>> On Thursday, 14 August 2014 at 07:07:59 UTC, Alex wrote:
>>> Invoking stuff is easy. I'd rather reimplement the communication to the dcd server instead to not get such a bottleneck if you're on windows or typing really fast. Executing an entire program for each keystroke is a real unsustainable solution, imho.
>>
>> https://github.com/Hackerpilot/DCD/blob/master/client.d#L72
>>
>> Alright. :-)
>
> Actually, someone has turned on the _"Enable Mixin & Template
> Mixin Analysis"_ options?
> Major drawbacks?

I did - basic stuff which was tested works :-P
https://github.com/aBothe/D_Parser/blob/master/Tests/ResolutionTests.cs#L3151-L3380
>
> Someone has turned _off_ the _"Only indent code lines instead of
> rearrange code parts"_?
> Major drawbacks?
I haven't implemented any new formatting features since indenting is totally satisfying for me. :-)