MetaTrader 5 Platform build 5326: Improvements and fixes - page 6

New comment
 

Dominik Egert #: I checked other function signatures, and there are incompatibilities given ... So, there needs to be some adjustment done on MQs side of things. 

Yes, many of the MQL5 functions are quite inconsistent regarding to datatype usage. That is a lack of rigour and discipline when it comes to MetaQuotes development.
 
Fernando Carreiro #:
Yes, many of the MQL5 functions are quite inconsistent regarding to datatype usage. That is a lack of rigour and discipline when it comes to MetaQuotes development.

If it just were possible for us to contribute to the documentation via comments or similar, we could fix a lot of confusions already. - I still dont understand why not at least we moderators could contribute with comments and code examples as well. It would be a much more comprehensive documentation, showing all the little quirks and whatch-outs on usage of certain functionality. 

I posted already an extensive list of all the little typos in the documented signatures, which still have not seen any updates.

 
Dominik Egert #: If it just were possible for us to contribute to the documentation via comments or similar, we could fix a lot of confusions already. - I still dont understand why not at least we moderators could contribute with comments and code examples as well. It would be a much more comprehensive documentation, showing all the little quirks and whatch-outs on usage of certain functionality. I posted already an extensive list of all the little typos in the documented signatures, which still have not seen any updates.

And I also wish there was a proper bug/issue tracking system, even if it would only be available for a select few, such as moderators and power users.

 
Dominik Egert #:

I checked other function signatures, and there are incompatibilities given

I asked you to check before reporting errors.

Forum on trading, automated trading systems and testing trading strategies

MetaTrader 5 Platform build 5326: Improvements and fixes

Dominik Egert, 2025.10.12 11:34

    uchar       uc_data[];
    uchar        c_data[];
    uchar       u_key[];
    uchar        key[];
 
fxsaber #:
I asked you to check before reporting errors.
?? What ??

Edit: you telling me its not an error?
 
fxsaber #:
I asked you to check before reporting errors.
You have not asked me to check before reporting errors. - You pointed out, the documentation is wrong. - Its either way an error. And I just posted additional confirmation on your statement.

 
Dominik Egert #:
?? What ??

Edit: you telling me its not an error?
It's actually not clear what you are reporting. 😉
 
Dominik Egert #: ?? What ?? Edit: you telling me its not an error?
I think what @fxsaber is suggesting is that it might not be an a bug but an documentation error. However, I did not check the specifics, so I am only speculating on the meaning of his words.
 
Fernando Carreiro #:
I think what @fxsaber is suggesting is that it might not be an a bug but an documentation error. However, I did not check the specifics, so I am only speculating on the meaning of his words.

What Dominik is reporting is the inconsistency of the signatures and compiler, it's not about the documentation (which is also often an issue).

Some function compiles fine with char/uchar, some others don't, while the signature is the same "const uchar&[]" for example.

 
@Alain Verleyen #: What Dominik is reporting is the inconsistency of the signatures and compiler, it's not about the documentation (which is also the issue). Some function compiles fine with char/uchar, some others don't, while the signature is the same "const uchar&[]" for example.
Yes, I fully understood @Dominik Egert posts, but I did not understand @fxsaber either. That is why I speculated on what he might have meant by his posts.
1234567891011
New comment