I found a nice documentation website :
http://docs.autodesk.com/FBX/2014/ENU/FBX-SDK-Documentation/index.html?url=cpp_ref/_common_2_common_8cxx-example.html,topicNumber=cpp_ref__common_2_common_8cxx_example_htmlc507b7ce-aa2f-4c44-b08f-90c94f43730b

There is all sources of sample, and code is highlighted with link to methods docs.
I think it will be a good thing to have real unittest linked with the documentation of D, just because instead embedded samples we are sure that is executable as it (no missing import, syntax error,...).
It seems that is a bad idea to have specific code samples for the documentation, it's generally out of date,... Is it feasible to have docs that extract chunks of real unittest as samples?

On Wednesday, 14 August 2013 at 15:25:09 UTC, Flamaros wrote:
> I found a nice documentation website :
> http://docs.autodesk.com/FBX/2014/ENU/FBX-SDK-Documentation/index.html?url=cpp_ref/_common_2_common_8cxx-example.html,topicNumber=cpp_ref__common_2_common_8cxx_example_htmlc507b7ce-aa2f-4c44-b08f-90c94f43730b
>
> There is all sources of sample, and code is highlighted with link to methods docs.
> I think it will be a good thing to have real unittest linked with the documentation of D, just because instead embedded samples we are sure that is executable as it (no missing import, syntax error,...).
> It seems that is a bad idea to have specific code samples for the documentation, it's generally out of date,... Is it feasible to have docs that extract chunks of real unittest as samples?

D has documented unit tests (Documented Unittests section at http://dlang.org/unittest.html) but they're a relatively new feature so most of the documentation doesn't yet use them.

On Saturday, 10 August 2013 at 17:29:40 UTC, Ruslan Mullakhmetov
wrote:
> clip
>
> Let me put my two cents at this thread, hope it would be useful.
>
> (1) The thread went (from the start) to discussion of technical details, not content discussion, and users are interested in content itself, which, IMHO is not optimally organized.
>
> clip

Motiviated by Ruslan's comments I thought I would make a
suggestion I had been thinking of with regards to the Forums. The
Forums organization seems a bit out of date. For example there
are a number of topics that are rarely ever receive posts, but
they appear before busy forums, such as D.learn. I wonder if this
might be one of the reasons why obvious learner questions get
posted to digitialmars.D on occassion. Any easy way to deal with
this would be to sort forums by post count rather than
alphabetically, but that has its own issues.


Perhaps the D forums could be split into two separate headings:

1. D Programming - general D related programming questions could
go here. It could include:
-  D.learn (More focused for newer D users)
-  D.phobos (questions about use of standard library)
-  D.programming (more advanced questions)
-  Debugging/Profiling (was digitalmars.D.debugger - on first
reading sounds like the forum is

2. D Development (this isn't a great name - but it would include
forums
more focused on the Development of the D language). Some topics
might
include:
- current digitalmars.D forum
- announce
- digitalmars.D.bugs
- digitalmars.D.ldc
- D.gnu
- dmd-beta
- dmd-concurrency
- dmd-internals
- phobos
- D-runtime

I exclusively use the Forum's and perhaps such a reorganization
would be too much trouble for folks who uses newreaders/email,
but I thought I would but the suggestion out there.