Re: Best practices for reading public interfaces

2015-02-22 Thread MrSmith via Digitalmars-d-learn
On Saturday, 21 February 2015 at 20:46:09 UTC, Kenny wrote: I like D modules and it's a major point in the list of major points why I like D (there is also the second not so nice wft-list but it's for another post). I'm annoyed with C++ includes and I'm tired to create 2 files every time when I

Re: Best practices for reading public interfaces

2015-02-22 Thread Kenny via Digitalmars-d-learn
On Sunday, 22 February 2015 at 12:13:02 UTC, MrSmith wrote: You can also fold all the function bodies in your editor, this helps me to read massive sources. Oh, I almost forgot about this feature, never used it in C++ but for D it looks promising. Thanks!

Re: Best practices for reading public interfaces

2015-02-22 Thread Kenny via Digitalmars-d-learn
On Saturday, 21 February 2015 at 20:56:26 UTC, anonymous wrote: On Saturday, 21 February 2015 at 20:46:09 UTC, Kenny wrote: b) Write DDocs and read documentation. The problem here is that I'm going to use D only for my own projects and in the last time I tend to write less documentation, for

Re: Best practices for reading public interfaces

2015-02-22 Thread ketmar via Digitalmars-d-learn
On Sun, 22 Feb 2015 16:12:49 +, Kenny wrote: On Saturday, 21 February 2015 at 20:56:26 UTC, anonymous wrote: On Saturday, 21 February 2015 at 20:46:09 UTC, Kenny wrote: b) Write DDocs and read documentation. The problem here is that I'm going to use D only for my own projects and in the

Best practices for reading public interfaces

2015-02-21 Thread Kenny via Digitalmars-d-learn
I like D modules and it's a major point in the list of major points why I like D (there is also the second not so nice wft-list but it's for another post). I'm annoyed with C++ includes and I'm tired to create 2 files every time when I need to add something new to the project... But I must admit

Re: Best practices for reading public interfaces

2015-02-21 Thread anonymous via Digitalmars-d-learn
On Saturday, 21 February 2015 at 20:46:09 UTC, Kenny wrote: b) Write DDocs and read documentation. The problem here is that I'm going to use D only for my own projects and in the last time I tend to write less documentation, for example I do not write it for the most methods of Vector3D. If