Discussion of article "Auto-Generated Documentation for MQL5 Code" - page 2

 

It seems to be generally accepted @param instead of \param for compatibility with other docogenerators.

It will be great if we adopt this standard at the MQL level, because the present style of code commenting is strange - a lot of unnecessary //////.

And if we add support at MetaEditor level, as it is done in Eclipse.... mmm....

 
Very good article, thanks.
 

Version 1.8.7 is the latest with MQL support.

The bug is somewhere among these commits.

Who finds it, please let me know.

 
Roffild:

Version 1.8.7 is the latest with MQL support.

The bug is somewhere among these commits.

Who finds it, please let me know.

Thanks. I have searched everything while I was struggling with the latest versions( Yes, it does not go higher than 1.8.7. On the commits I have not understood what the catch is(
 
Alain Verleyen:
Very good article, thanks.
 
Now I took the old config, which was created before version 1.8.8, and fixed it:
EXTENSION_MAPPING      = mq5=C++ mqh=C++
Works!!!111
 
MetaQuotes Software Corp.:

New article Auto-Generated Documentation for MQL5 Code is published:

Author: Paul

Is anybody able to use it in 2019 (latest version)   ...i followed the article and I'm not able to have class list generated.

Regards

 
Marcin Rutkowski:

Is anybody able to use it in 2019 (latest version)   ...i followed the article and I'm not able to have class list generated.

Regards

Were you able to achieve it?

 
As it was said earlier, on the Input tab you set INPUT_ENCODING as windows-1251. And there are no problems with encodings, everything is clear