MetaEditor v. 4585 compiler breaks previousy working code! - page 2

 
Fantiago #:
instead of fiddling with a working compiler for no discernible benefit

[Translated via Google Translate]

Форум по трейдингу, автоматическим торговым системам и тестированию торговых стратегий

Новая версия платформы MetaTrader 5 build 4410: улучшения в работе

Renat Fatkhullin, 2024.08.11 22:25

Our plans for MQL5 and MetaEditor:

  1. release a new more efficient compiler (step by step)
  2. include OpenBLAS math libraries in MQL5
  3. switch editor from subversion to Git
  4. launch a GitHub analogue for traders - MQL5 Algo Forge, the project is already available, we are waiting for Git to complete in the editor
  5. add native compilation of c/c++ projects directly in the editor, it's already close
  6. expand mqproj project settings to handle large projects in different languages
  7. add imported modules and a single repository to simplify and speed up development
 
Vladislav Boyko #:

Of course, you can set priorities for someone else's business better than people who have been successfully running it for about 30 years. Especially considering the fact that you are not paying for the implementation of the functionality you ask for.


Judging by MQ's public statements, the main priority now is the development of a new compiler.

If I'm not mistaken, they also said that they were going to improve the metaeditor, but after developing a new compiler. They also abandoned the subversion storage in favor of a git based storage and will continue to develop this in the future along with improving the functionality of the projects.

And you complain that the compiler is now more strict about your incorrectly written code.

Very good answer
 
Vladislav Boyko #:

udging by MQ's public statements, the main priority now is the development of a new compiler.

If I'm not mistaken, they also said that they were going to improve the metaeditor, but after developing a new compiler. They also abandoned the subversion storage in favor of a git based storage and will continue to develop this in the future along with improving the functionality of the projects.

And you complain that the compiler is now more strict about your incorrectly written code.

Very bad answer, because:


1. The code has been correct since the inception of MT5. That it now suddenly throws errors is not a law of nature, but a political choice. If at all, it should be a warning and more descriptive. Also, developent time spent messing up people's working codes is development time badly spent, while many basic features, especially in MeatEditor, are still acutely missing.


2. I think you are mistaken that they were going to improve MetaEditor, or it was announced so long ago that you forgot. Are you a masochist who likes to wait like 30 years for announced improvements to actually come about?


Constructive criticism is not to be feared. I have no interest in running down MetaQuotes, on the contrary, I am thankful and am not shy to say so.


But I'm also not shy to voice constructive criticism.


Are you?

 
Fantiago #:

Very bad answer, because:

1. The code has been correct since the inception of MT5. That it now suddenly throws errors is not a law of nature, but a political choice. If at all, it should be a warning and more descriptive. Also, developent time spent messing up people's working codes is development time badly spent, while many basic features, especially in MeatEditor, are still acutely missing.

2. I think you are mistaken that they were going to improve MetaEditor, or it was announced so long ago that you forgot. Are you a masochist who likes to wait like 30 years for announced improvements to actually come about?

Constructive criticism is not to be feared. I have no interest in running down MetaQuotes, on the contrary, I am thankful and am not shy to say so.

But I'm also not shy to voice constructive criticism.

Are you?

The world is constantly changing and evolving. The code that everyone writes today will become wildly legacy in a few years.

You can take those errors either as a hint to improve your code and skills, or as a spoke in the wheel. The choice is yours. But you have to make a choice: either evolve with the rest of the world, or grumble.

A person who understands what the problem is (we tried to explain it to you here) and knows a couple of hot keys will need no more than 3 minutes to fix your 20 errors.