www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.announce - DDT 0.5.0 ("Creamfields") released

reply Bruno Medeiros <brunodomedeiros+spam com.gmail> writes:
DDT 0.5.0 (codename "Creamfields") has been released. (Yes, as treat I 
decided to giving ocasional release name :P)

This new release requires DLTK 3.0 (from Indigo), so if you are going 
for the upgrade path, you need to add the new DLTK update site:
http://download.eclipse.org/releases/indigo

Right Next on the TODO list is debugger support. Well, after the minor 
internal task of switching the source repository from Mercurial to Git, 
now that Google Code supports Git.

Changelog ( 
http://code.google.com/a/eclipselabs.org/p/ddt/wiki/ChangeLog#DDT_0.
.0_%282011-08-26%29 
)

== DDT 0.5.0 (2011-08-26) ==
  * Updated DDT to DTLK 3.0
  * Made icons of D source elements (classes, structs templates, etc.) 
consistent throughout the UI.
    * (Previously DLTK views and some popups used simplified icons, and 
only CA and outline used more detailed icons.)
  * Outline view changes:
    * Now shows nested elements.
    * Clicking on named elements correctly selects their name in the 
editor (previously it just revealed the element).
    * Added context menu to the outline elements, added some filter 
actions to the toolbar of the view.
  * Constructor/Desctructors/Allocators/Deallocators now show up in 
Outline view and quick Outline.

also anonymous classes.
  * Fix in Documentation hovers: removed redudant text, and now displays 
concrete archetype (Class, Interface, Struct, Union), instead of 
"Aggregate".

still be missing though.
  * Fixed some minor NPE and assertion failure bugs.


workaround hack).


to be applied.


-- 
Bruno Medeiros - Software Engineer
Aug 26 2011
next sibling parent Tom <tom nospam.com> writes:
El 26/08/2011 15:13, Bruno Medeiros escribió:

 DDT 0.5.0 (codename "Creamfields") has been released. (Yes, as treat I
 decided to giving ocasional release name :P)

 This new release requires DLTK 3.0 (from Indigo), so if you are going
 for the upgrade path, you need to add the new DLTK update site:
 http://download.eclipse.org/releases/indigo

 Right Next on the TODO list is debugger support. Well, after the minor
 internal task of switching the source repository from Mercurial to Git,
 now that Google Code supports Git.

 Changelog (
 http://code.google.com/a/eclipselabs.org/p/ddt/wiki/ChangeLog#DDT_0.5.0_%282011-08-26%29
 )

 == DDT 0.5.0 (2011-08-26) ==
 * Updated DDT to DTLK 3.0
 * Made icons of D source elements (classes, structs templates, etc.)
 consistent throughout the UI.
 * (Previously DLTK views and some popups used simplified icons, and only
 CA and outline used more detailed icons.)
 * Outline view changes:
 * Now shows nested elements.
 * Clicking on named elements correctly selects their name in the editor
 (previously it just revealed the element).
 * Added context menu to the outline elements, added some filter actions
 to the toolbar of the view.
 * Constructor/Desctructors/Allocators/Deallocators now show up in
 Outline view and quick Outline.

 also anonymous classes.
 * Fix in Documentation hovers: removed redudant text, and now displays
 concrete archetype (Class, Interface, Struct, Union), instead of
 "Aggregate".

 still be missing though.
 * Fixed some minor NPE and assertion failure bugs.


 workaround hack).


 be applied.


Great news! Thank you very much.

Tom;
Aug 26 2011
prev sibling next sibling parent reply Bernard Helyer <b.helyer gmail.com> writes:
Good stuff. Nice to see Indigo support.
Aug 30 2011
parent reply Bernard Helyer <b.helyer gmail.com> writes:
On Tue, 30 Aug 2011 11:57:48 +0000, Bernard Helyer wrote:


 Good stuff. Nice to see Indigo support.


I'm seeing some serious performance problems (Eclipse typing lagging and 
stuttering when working with templates and structs and big files in 
general). Anyone else seeing this?
Sep 01 2011
next sibling parent reply Bruno Medeiros <brunodomedeiros+spam com.gmail> writes:
On 01/09/2011 08:19, Bernard Helyer wrote:

 I'm seeing some serious performance problems (Eclipse typing lagging and
 stuttering when working with templates and structs and big files in
 general). Anyone else seeing this?


If you can isolate the problem, that would be quite helpful. It helps 
that you have a simple Eclipse installation with just DDT as a 
third-party plugins, just to make sure it is not other plugins that 
could be causing the issue.
Also, is this something you've notice only on this release? Was the 
previous release working fine?

-- 
Bruno Medeiros - Software Engineer
Sep 06 2011
parent reply Bernard Helyer <b.helyer gmail.com> writes:
On Tue, 06 Sep 2011 15:10:42 +0100, Bruno Medeiros wrote:


 On 01/09/2011 08:19, Bernard Helyer wrote:

 I'm seeing some serious performance problems (Eclipse typing lagging
 and stuttering when working with templates and structs and big files in
 general). Anyone else seeing this?


 
 If you can isolate the problem, that would be quite helpful. It helps
 that you have a simple Eclipse installation with just DDT as a
 third-party plugins, just to make sure it is not other plugins that
 could be causing the issue.
 Also, is this something you've notice only on this release? Was the
 previous release working fine?


The previous release was fine. DDT is the only thing installed. It seems 
to manifest the worst when working on the same file with multiple editor 
views.
Sep 07 2011
parent reply Bruno Medeiros <brunodomedeiros+spam com.gmail> writes:
On 07/09/2011 13:58, Bernard Helyer wrote:

 On Tue, 06 Sep 2011 15:10:42 +0100, Bruno Medeiros wrote:


 On 01/09/2011 08:19, Bernard Helyer wrote:

 I'm seeing some serious performance problems (Eclipse typing lagging
 and stuttering when working with templates and structs and big files in
 general). Anyone else seeing this?


 If you can isolate the problem, that would be quite helpful. It helps
 that you have a simple Eclipse installation with just DDT as a
 third-party plugins, just to make sure it is not other plugins that
 could be causing the issue.
 Also, is this something you've notice only on this release? Was the
 previous release working fine?


 The previous release was fine. DDT is the only thing installed. It seems
 to manifest the worst when working on the same file with multiple editor
 views.


(sorry for the delay in replying, I haven't had much time for D stuff 
lately). Could you sent me one such file so that I try to replicate the 
issue? I quickly tried to replicate it with a big file 
(http://code.google.com/a/eclipselabs.org/p/ddt/source/browse/org.dsource.ddt.ide.core/testdata/sa
pleSrcBig/bigfile.d 
) like that, with multiple editors for the same file, but didn't notice 
any issues. Also, let me know what your folding preferences are (small 
suspicion it might be related to this).


-- 
Bruno Medeiros - Software Engineer
Sep 21 2011
parent reply Bernard Helyer <b.helyer gmail.com> writes:
I was wrong about the multiple editor thing, but you were spot on about 
the folding. Disabling it made all the hitches go away. Thanks.
Sep 21 2011
parent reply Bernard Helyer <b.helyer gmail.com> writes:
On Thu, 22 Sep 2011 06:47:18 +0000, Bernard Helyer wrote:


 I was wrong about the multiple editor thing, but you were spot on about
 the folding. Disabling it made all the hitches go away. Thanks.


Spoke too soon. It seems to be related to errors parsing or something. 
I'll try and get you a test case.
Sep 21 2011
parent Bruno Medeiros <brunodomedeiros+spam com.gmail> writes:
On 22/09/2011 07:48, Bernard Helyer wrote:

 On Thu, 22 Sep 2011 06:47:18 +0000, Bernard Helyer wrote:


 I was wrong about the multiple editor thing, but you were spot on about
 the folding. Disabling it made all the hitches go away. Thanks.


 Spoke too soon. It seems to be related to errors parsing or something.
 I'll try and get you a test case.


Yes, please do, I welcome such a bug report. (Even if folding made the 
issue go away in any scenario, it would still be an issue)

-- 
Bruno Medeiros - Software Engineer
Sep 29 2011
prev sibling parent reply "Marco Leise" <Marco.Leise gmx.de> writes:
Am 01.09.2011, 09:19 Uhr, schrieb Bernard Helyer <b.helyer gmail.com>:


 On Tue, 30 Aug 2011 11:57:48 +0000, Bernard Helyer wrote:


 Good stuff. Nice to see Indigo support.


 I'm seeing some serious performance problems (Eclipse typing lagging and
 stuttering when working with templates and structs and big files in
 general). Anyone else seeing this?


Yes, I can definitely type faster than my CPU can handle DDT. :D
I'm close to switching to a pure text editor, but then again, I could  
first try to disable some features.
Also I realized that non-ASCII characters are sometimes errors where DMD  
would not complain. Sometimes when the non-ASCII is inside an identifier,  
not at the start or end.
Oct 17 2011
next sibling parent Bernard Helyer <b.helyer gmail.com> writes:
On Tue, 18 Oct 2011 07:39:30 +0200, Marco Leise wrote:


 Yes, I can definitely type faster than my CPU can handle DDT. :D I'm
 close to switching to a pure text editor, but then again, I could first
 try to disable some features.


Yeah, I switched to emacs for the moment, as DDT is too painful to use.
Oct 18 2011
prev sibling parent Bruno Medeiros <brunodomedeiros+spam com.gmail> writes:
On 18/10/2011 06:39, Marco Leise wrote:

 Am 01.09.2011, 09:19 Uhr, schrieb Bernard Helyer <b.helyer gmail.com>:


 On Tue, 30 Aug 2011 11:57:48 +0000, Bernard Helyer wrote:


 Good stuff. Nice to see Indigo support.


 I'm seeing some serious performance problems (Eclipse typing lagging and
 stuttering when working with templates and structs and big files in
 general). Anyone else seeing this?


 Yes, I can definitely type faster than my CPU can handle DDT. :D
 I'm close to switching to a pure text editor, but then again, I could
 first try to disable some features.
 Also I realized that non-ASCII characters are sometimes errors where DMD
 would not complain. Sometimes when the non-ASCII is inside an
 identifier, not at the start or end.


I would really welcome some test cases, so that I could try this myself, 
and identify the issue. I know the current parser has several 
performance issues (known and unknown ones), but at least there should 
not be performance regressions (getting worse in new versions).

-- 
Bruno Medeiros - Software Engineer
Oct 20 2011
prev sibling next sibling parent Jay Norwood <jayn prismnet.com> writes:
DDT is a great help in learning about how the D language is used by providing 
the ability to poke around in the library code ... especially the ability to
find all references and opening the definitions.  I'm using VisualD for debug,
but DDT for editing due to its superior completion and context pop-up help. 
Thanks a lot.
Oct 19 2011
prev sibling parent reply Trass3r <un known.com> writes:
Does DDT use a separate thread for parsing?
Editing bigger files can be extremely laggy.
Nov 27 2011
parent reply Bruno Medeiros <brunodomedeiros+spam com.gmail> writes:
On 27/11/2011 18:29, Trass3r wrote:

 Does DDT use a separate thread for parsing?
 Editing bigger files can be extremely laggy.


It does use a separate thread for parsing (standard practice with any 
Eclipse IDE). Doesn't mean there can't be issues causing laggyness.

I'm getting increasingly concerned with these reports of DDT becoming 
slow when editing large files, but I don't know how to replicate them (I 
don't program in D with large enough files to ever come across it), so 
unless someone gives me some test data - the files they are editing, 
machine specs, what they were doing (just typing or also doing content 
assist, etc.) - it will be very hard to address this issue!

-- 
Bruno Medeiros - Software Engineer
Dec 01 2011
next sibling parent reply Trass3r <un known.com> writes:
 Does DDT use a separate thread for parsing?
 Editing bigger files can be extremely laggy.


 It does use a separate thread for parsing (standard practice with any  
 Eclipse IDE). Doesn't mean there can't be issues causing laggyness.

 I'm getting increasingly concerned with these reports of DDT becoming  
 slow when editing large files, but I don't know how to replicate them (I  
 don't program in D with large enough files to ever come across it), so  
 unless someone gives me some test data - the files they are editing,  
 machine specs, what they were doing (just typing or also doing content  
 assist, etc.) - it will be very hard to address this issue!


Ok, I'll try to come up with some test set the next time I experience this.

btw, 2 other small issues:
- if you use autocompletion when the cursor is at the start of another  
identifier, it overwrites it instead of inserting.

So the cursor is left to foo, I press Ctrl+Space, choose something and it  
overwrites foo.
Partial completion works correctly though: |foo -> dem|foo -> Ctrl+Space  
-> demangle|foo -> I choose my own demangleBla -> demangleBla| -> no foo  
anymore

- Is there a way to disable automatic builds on every save?
I currently just delete the response file contents in D Compile Options  
and replace the command with echo "ok".
Dec 01 2011
next sibling parent reply "Marco Leise" <Marco.Leise gmx.de> writes:
Am 01.12.2011, 17:54 Uhr, schrieb Trass3r <un known.com>:


 btw, 2 other small issues:
 - if you use autocompletion when the cursor is at the start of another  
 identifier, it overwrites it instead of inserting.


That is actually a matter of preference - believe it or not! Some IDEs  
offer the option to either insert or overwrite on auto-complete.

My personal wish list is:
- Check Unicode identifiers. They are sometimes confusing the parser. (I  
should post example code here, really.)
- Inference of 'auto' types like 'x' in 'foreach (ref x; list)'
- I am using a symlinked Makefile in my projects instead of the build.rf.  
It's not like I'm doing anything fancy there for a debug build, but it has  
the advantage that updates to the options are propagated to all projects  
and I have the other targets (profile, unittest, release, ...) all in one  
place. Some way to support a custom Makefile build would be nice, even  
though the auto-generated script is quite handy to get started with D.
- GDB support would be awesome of course, but no hurry.
Dec 01 2011
next sibling parent reply Trass3r <un known.com> writes:
 btw, 2 other small issues:
 - if you use autocompletion when the cursor is at the start of another  
 identifier, it overwrites it instead of inserting.


 That is actually a matter of preference - believe it or not! Some IDEs  
 offer the option to either insert or overwrite on auto-complete.


If you want overwrite mode, press your INS key ;)
I'm ok with it becoming an option, but the default has to be insertion.


 - GDB support would be awesome of course, but no hurry.


Already done in trunk.
Dec 01 2011
parent reply Gyula Gubacsi <gyula.gubacsi gmail.com> writes:
I think it's GDC what you mean. And that's already good news. You could
perhaps try somehow use the CDT's implementation of the GDB debugger
communication, but GDB doesn't support D anywhere near to be usefully
comfortable so there's a little gap in the toolchain atm, unfortunately.

On 1 December 2011 19:07, Trass3r <un known.com> wrote:


 btw, 2 other small issues:

 - if you use autocompletion when the cursor is at the start of another
 identifier, it overwrites it instead of inserting.


 That is actually a matter of preference - believe it or not! Some IDEs
 offer the option to either insert or overwrite on auto-complete.


 If you want overwrite mode, press your INS key ;)
 I'm ok with it becoming an option, but the default has to be insertion.


  - GDB support would be awesome of course, but no hurry.


 Already done in trunk.





 Dec 01 2011



  parent  Trass3r <un known.com>  writes:


 I think it's GDC what you mean


Indeed.



 Dec 01 2011



prev sibling next sibling parent  Gyula Gubacsi <gyula.gubacsi gmail.com>  writes:


I'm looking in to the type inference thing but it could take for a
while to implement it.
On the GDB issue I'm afraid GDB support isn't in the best shape yet,
but hopefully it would change at some point. Without a decent D
support of GDB maybe it won't be exactly the best experience, but
perhaps we should utilitize the CDT's GDB interface. see here:
http://groups.google.com/group/ddt-ide/browse_thread/thread/619e8192e9fb6ca=
3
and this:

Main problem - D DWARF extensions:
http://d.puremagic.com/issues/show_bug.cgi?id=3D4180

Second: we should provide unittests for gdb for all basic test case
for DMD/GDC/LDC. I start write it (you can try search patch in
gdb-patches archive). But it cannot be done before than we resolve
conflict with DWARF. DMD/GDC/LDC provide slightly different debug
information. We should contact with compiler dev teams and try unify
debug information (IMHO it should by close as possible to C/C++ form
GCC).

Third: add support associative arrays and other D specific =A0features.

You can see all registered problems in debug information for DMD:
http://d.puremagic.com/issues/show_bug.cgi?id=3D4044

Feel free to ask me about this subj. If I can I try help, but I am not
DWARF/GDB expert ;)

2011/11/8, Gyula Gubacsi <gyula.gubacsi gmail.com>:


 Hi,

 I was directed to you from the GDB mailing list as I was trying to get so=


me

 information about what is the progress on D support in GDB. As I understa=


nd

 the only D specific extension was to add the dynamic arrays (I reckon,
 extension compared to C) and the name mangling rules.

 I am a newbie contributor to the DDT Eclipse plug-in project which doesn'=


t

 make much sense without a useful, multi-platform command-line debugger an=


d

 so far I couldn't find alternative to GDB. In fact, given that the GDB
 communication is already solved in the CDT plug-in, it would be the best
 idea to use the GDB.

 However, I had difficulties using GDB with D programs. I am willing to
 improve the D support in GDB but I need some description what should I
 start with, and what are the critical issues implementing a language
 interface for GDB.

 I hope you can clarify some issues if you have some time to write me.

 Sincerely

 Gyula Gubacsi / progician


I'm maybe overambitious over my time though :D


On 1 December 2011 18:29, Marco Leise <Marco.Leise gmx.de> wrote:

 Am 01.12.2011, 17:54 Uhr, schrieb Trass3r <un known.com>:



 btw, 2 other small issues:
 - if you use autocompletion when the cursor is at the start of another i=




dentifier, it overwrites it instead of inserting.

 That is actually a matter of preference - believe it or not! Some IDEs of=


fer the option to either insert or overwrite on auto-complete.

 My personal wish list is:
 - Check Unicode identifiers. They are sometimes confusing the parser. (I =


should post example code here, really.)

 - Inference of 'auto' types like 'x' in 'foreach (ref x; list)'
 - I am using a symlinked Makefile in my projects instead of the build.rf.=


 It's not like I'm doing anything fancy there for a debug build, but it has=
 the advantage that updates to the options are propagated to all projects a=
nd I have the other targets (profile, unittest, release, ...) all in one pl=
ace. Some way to support a custom Makefile build would be nice, even though=
 the auto-generated script is quite handy to get started with D.

 - GDB support would be awesome of course, but no hurry.





 Dec 01 2011



prev sibling  parent  Jacob Carlborg <doob me.com>  writes:


On 2011-12-01 19:29, Marco Leise wrote:

 Am 01.12.2011, 17:54 Uhr, schrieb Trass3r <un known.com>:


 btw, 2 other small issues:
 - if you use autocompletion when the cursor is at the start of another
 identifier, it overwrites it instead of inserting.


 That is actually a matter of preference - believe it or not! Some IDEs
 offer the option to either insert or overwrite on auto-complete.


Eclipse has that option, I don't know if it's for all editors or just 
for JDT.

-- 
/Jacob Carlborg



 Dec 01 2011



prev sibling next sibling parent reply Trass3r <un known.com>  writes:


 btw, 2 other small issues:


Oh just found out DDT gets confused by parens in strings:

symName.startsWith("PROVIDE ("))



 Dec 01 2011



  parent  "Marco Leise" <Marco.Leise gmx.de>  writes:


Am 01.12.2011, 20:35 Uhr, schrieb Trass3r <un known.com>:


 btw, 2 other small issues:


 Oh just found out DDT gets confused by parens in strings:

 symName.startsWith("PROVIDE ("))


It also doesn't like:

enum maxGroupNumber = 2^^19; // <- Syntax error on token "^", Expression  
expected after this token



 Dec 02 2011



prev sibling  parent  Bruno Medeiros <brunodomedeiros+spam com.gmail>  writes:


On 01/12/2011 16:54, Trass3r wrote:

 Does DDT use a separate thread for parsing?
 Editing bigger files can be extremely laggy.


 It does use a separate thread for parsing (standard practice with any
 Eclipse IDE). Doesn't mean there can't be issues causing laggyness.

 I'm getting increasingly concerned with these reports of DDT becoming
 slow when editing large files, but I don't know how to replicate them
 (I don't program in D with large enough files to ever come across it),
 so unless someone gives me some test data - the files they are
 editing, machine specs, what they were doing (just typing or also
 doing content assist, etc.) - it will be very hard to address this issue!


 Ok, I'll try to come up with some test set the next time I experience this.

 btw, 2 other small issues:
 - if you use autocompletion when the cursor is at the start of another
 identifier, it overwrites it instead of inserting.

 So the cursor is left to foo, I press Ctrl+Space, choose something and
 it overwrites foo.
 Partial completion works correctly though: |foo -> dem|foo -> Ctrl+Space
 -> demangle|foo -> I choose my own demangleBla -> demangleBla| -> no foo
 anymore


Go to Preferences/DDT/Editor/Content Assist, change option "Completion 
Overwrites", to "Completion Inserts", and there you go. The default 
shall remain "Completion Overwrites" though, as I think that is more 
sensible. (even though in JDT the default is inserts :p )

Partial completion should always work according to this preference 
setting, so it's a bug that it always inserts. Opened:
http://code.google.com/a/eclipselabs.org/p/ddt/issues/detail?id=69


 - Is there a way to disable automatic builds on every save?
 I currently just delete the response file contents in D Compile Options
 and replace the command with echo "ok".


Go to Project in the main menu, deselect "Build automatically". Note, 
this is a workspace-global setting, nor per project. So now if you want 
to build use the menu or press "Ctrl-B" to start a workspace build: all 
projects whose resources have changed since the last build will be built.

-- 
Bruno Medeiros - Software Engineer



 Dec 06 2011



prev sibling next sibling parent reply Jacob Carlborg <doob me.com>  writes:


On 2011-12-01 16:18, Bruno Medeiros wrote:

 On 27/11/2011 18:29, Trass3r wrote:

 Does DDT use a separate thread for parsing?
 Editing bigger files can be extremely laggy.


 It does use a separate thread for parsing (standard practice with any
 Eclipse IDE). Doesn't mean there can't be issues causing laggyness.

 I'm getting increasingly concerned with these reports of DDT becoming
 slow when editing large files, but I don't know how to replicate them (I
 don't program in D with large enough files to ever come across it), so
 unless someone gives me some test data - the files they are editing,
 machine specs, what they were doing (just typing or also doing content
 assist, etc.) - it will be very hard to address this issue!


Well, just put a large library in a project, like Phobos, Tango or DWT. 
std.datetime in Phobos is 35+k lines of code. Then try different 
features like autocompletion and similar.

-- 
/Jacob Carlborg



 Dec 01 2011



  parent reply Bruno Medeiros <brunodomedeiros+spam com.gmail>  writes:


On 01/12/2011 17:44, Jacob Carlborg wrote:

 On 2011-12-01 16:18, Bruno Medeiros wrote:

 On 27/11/2011 18:29, Trass3r wrote:

 Does DDT use a separate thread for parsing?
 Editing bigger files can be extremely laggy.


 It does use a separate thread for parsing (standard practice with any
 Eclipse IDE). Doesn't mean there can't be issues causing laggyness.

 I'm getting increasingly concerned with these reports of DDT becoming
 slow when editing large files, but I don't know how to replicate them (I
 don't program in D with large enough files to ever come across it), so
 unless someone gives me some test data - the files they are editing,
 machine specs, what they were doing (just typing or also doing content
 assist, etc.) - it will be very hard to address this issue!


 Well, just put a large library in a project, like Phobos, Tango or DWT.
 std.datetime in Phobos is 35+k lines of code. Then try different
 features like autocompletion and similar.


I'll try something like this, eventually. But we know that the 
performance of the parser is not that good.
What I was more concerned about, at least in more immediate terms, is 
significant performance regressions. That is, stuff that has gotten 
significantly slower with newer DDT releases... that shouldn't be 
happening at all. But a performance bug could have been introduced.

-- 
Bruno Medeiros - Software Engineer



 Jan 17 2012



  parent reply "#code" <supetronix.dev1 gmail.com>  writes:


All this seems really good but am I the only one that's getting 
error to download DDT in eclilpse? When I tried following link on 
unbuntu eclipse then I am getting error:

http://ddt.eclipselabs.org.codespot.com/git.updates/

error:

Artifact not found: 
http://ddt.eclipselabs.org.codespot.com/git.updates/content.jar.
Artifact not found: 
http://ddt.eclipselabs.org.codespot.com/git.updates/content.jar.
http://ddt.eclipselabs.org.codespot.com/git.updates/content.jar


Am I missing something?

Thanks


On Tuesday, 17 January 2012 at 15:52:24 UTC, Bruno Medeiros wrote:

 On 01/12/2011 17:44, Jacob Carlborg wrote:

 On 2011-12-01 16:18, Bruno Medeiros wrote:

 On 27/11/2011 18:29, Trass3r wrote:

 Does DDT use a separate thread for parsing?
 Editing bigger files can be extremely laggy.


 It does use a separate thread for parsing (standard practice 
 with any
 Eclipse IDE). Doesn't mean there can't be issues causing 
 laggyness.

 I'm getting increasingly concerned with these reports of DDT 
 becoming
 slow when editing large files, but I don't know how to 
 replicate them (I
 don't program in D with large enough files to ever come 
 across it), so
 unless someone gives me some test data - the files they are 
 editing,
 machine specs, what they were doing (just typing or also 
 doing content
 assist, etc.) - it will be very hard to address this issue!


 Well, just put a large library in a project, like Phobos, 
 Tango or DWT.
 std.datetime in Phobos is 35+k lines of code. Then try 
 different
 features like autocompletion and similar.


 I'll try something like this, eventually. But we know that the 
 performance of the parser is not that good.
 What I was more concerned about, at least in more immediate 
 terms, is significant performance regressions. That is, stuff 
 that has gotten significantly slower with newer DDT releases... 
 that shouldn't be happening at all. But a performance bug could 
 have been introduced.





 May 18 2012



  parent reply Bruno Medeiros <brunodomedeiros+dng gmail.com>  writes:


On 19/05/2012 04:50, #code wrote:

 All this seems really good but am I the only one that's getting error to
 download DDT in eclilpse? When I tried following link on unbuntu eclipse
 then I am getting error:

 http://ddt.eclipselabs.org.codespot.com/git.updates/

 error:

 Artifact not found:
 http://ddt.eclipselabs.org.codespot.com/git.updates/content.jar.
 Artifact not found:
 http://ddt.eclipselabs.org.codespot.com/git.updates/content.jar.
 http://ddt.eclipselabs.org.codespot.com/git.updates/content.jar


 Am I missing something?

 Thanks



Are you still having this problem? AFAIK there is no issue with the 
update site, I haven't heard of anyone else having such a problem in the 
meanwhile.

-- 
Bruno Medeiros - Software Engineer



 May 30 2012



  parent reply "#coder" <supetronix.dev1 gmail.com>  writes:


Yes. I am still getting the same error. I am on ubuntu with 
eclipse 3.7.2.

http://ddt.eclipselabs.org.codespot.com/git.updates/

Errors are:

1.
Artifact not found: 
http://ddt.eclipselabs.org.codespot.com/git.updates/content.jar.
Artifact not found: 
http://ddt.eclipselabs.org.codespot.com/git.updates/content.jar.
http://ddt.eclipselabs.org.codespot.com/git.updates/content.jar

2.
No repository found at 
http://ddt.eclipselabs.org.codespot.com/git.updates/.



On Wednesday, 30 May 2012 at 15:59:33 UTC, Bruno Medeiros wrote:

 On 19/05/2012 04:50, #code wrote:

 All this seems really good but am I the only one that's 
 getting error to
 download DDT in eclilpse? When I tried following link on 
 unbuntu eclipse
 then I am getting error:

 http://ddt.eclipselabs.org.codespot.com/git.updates/

 error:

 Artifact not found:
 http://ddt.eclipselabs.org.codespot.com/git.updates/content.jar.
 Artifact not found:
 http://ddt.eclipselabs.org.codespot.com/git.updates/content.jar.
 http://ddt.eclipselabs.org.codespot.com/git.updates/content.jar


 Am I missing something?

 Thanks



 Are you still having this problem? AFAIK there is no issue with 
 the update site, I haven't heard of anyone else having such a 
 problem in the meanwhile.





 May 30 2012



  parent reply Bruno Medeiros <brunodomedeiros+dng gmail.com>  writes:


On 31/05/2012 06:04, #coder wrote:

 Yes. I am still getting the same error. I am on ubuntu with eclipse 3.7.2.

 http://ddt.eclipselabs.org.codespot.com/git.updates/

 Errors are:

 1.
 Artifact not found:
 http://ddt.eclipselabs.org.codespot.com/git.updates/content.jar.
 Artifact not found:
 http://ddt.eclipselabs.org.codespot.com/git.updates/content.jar.
 http://ddt.eclipselabs.org.codespot.com/git.updates/content.jar

 2.
 No repository found at
 http://ddt.eclipselabs.org.codespot.com/git.updates/.


Everything seems to be working fine here.
Check that it is not a problem with a proxy or strange firewall that 
prevents the Eclipse update/install from properly working. (try it on 
another network)

-- 
Bruno Medeiros - Software Engineer



 May 31 2012



  parent reply "Jarl =?UTF-8?B?QW5kcsOpIg==?= <jarl.andre gmail.com>  writes:


I have a "problem" with DDT. It seems that adding an "in 
contract" to an interface method is not recognized by DDT. It 
gives "Syntax error on token "}", ; expected after this token". 
Is this related to an existing bug?

interface SomeInterface {
     void setup(string someNiceParameter) in { 
enforce(someNiceParameter); }
}



 Jun 26 2012



  parent  "Jarl =?UTF-8?B?QW5kcsOpIg==?= <jarl.andre gmail.com>  writes:


On Tuesday, 26 June 2012 at 17:28:43 UTC, Jarl André wrote:

 I have a "problem" with DDT. It seems that adding an "in 
 contract" to an interface method is not recognized by DDT. It 
 gives "Syntax error on token "}", ; expected after this token". 
 Is this related to an existing bug?

 interface SomeInterface {
     void setup(string someNiceParameter) in { 
 enforce(someNiceParameter); }
 }


The code compiles of course, but I don't like reds in my IDE ;)



 Jun 26 2012



prev sibling  parent reply Ary Manzana <ary esperanto.org.ar>  writes:


On 12/1/11 12:18 PM, Bruno Medeiros wrote:

 On 27/11/2011 18:29, Trass3r wrote:

 Does DDT use a separate thread for parsing?
 Editing bigger files can be extremely laggy.


 It does use a separate thread for parsing (standard practice with any
 Eclipse IDE). Doesn't mean there can't be issues causing laggyness.

 I'm getting increasingly concerned with these reports of DDT becoming
 slow when editing large files, but I don't know how to replicate them (I
 don't program in D with large enough files to ever come across it), so
 unless someone gives me some test data - the files they are editing,
 machine specs, what they were doing (just typing or also doing content
 assist, etc.) - it will be very hard to address this issue!


Descent also started to work slowly with large files.

In my humble opinion, the problem is not the editor. If you have to edit 
a file 8000 lines long, then something's wrong with either how you 
program or the language (too verbose? not too compact?).

Might also be a problem with Eclipse... though I remember editing Java 
files that long and it worked more or less OK.



 Dec 02 2011



  parent  Jacob Carlborg <doob me.com>  writes:


On 2011-12-02 17:24, Ary Manzana wrote:


 Descent also started to work slowly with large files.

 In my humble opinion, the problem is not the editor. If you have to edit
 a file 8000 lines long, then something's wrong with either how you
 program or the language (too verbose? not too compact?).


I completely agree with you, but it may be someone else code. 
std.datetime in Phobos is around 35+k lines of code, that's just 
completely mad in my opinion. The OS module in DWT/SWT is around 10k 
lines of code. Most of that code consists of declarations of OS specific 
functions, I guess they wanted to keep that in one file.

-- 
/Jacob Carlborg



 Dec 04 2011