Errors, bugs, questions - page 2555
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
add FILE_SHARE_READ for write handle and FILE_SHARE_WRITE for read handle
Doesn't work, only individually if hung on the chart. Used:
Doesn't work, only individually if hung on the chart. Used:
All solved.Used:
build 2135 is broken at all
'GENERATE_VECTOR' - unexpected token, probably type is missing? 1_mystd.mqh 74 1
'GENERATE_VECTOR' - unexpected token, probably type is missing? 1_mystd.mqh 75 1
'GENERATE_VECTOR' - variable already defined 1_mystd.mqh 75 1Compiled for ages, broke in the new build.
build 2135 is broken.
It's been compiling for ages, it's broken in the new build.
used to eat the compiler, but in the new build it refused, they must have tweaked something (well I don't think I accidentally deleted a zero).
I cheat, it's fine, one of the abortions was called in the form of
The compiler used to eat it up, but in the new build it has refused, so they must have tweaked something (well, I don't think I accidentally deleted a zero).
By the way, we must ask developers to introduce an inline abort, abort ... and ideally, of course, exceptions. But at least start with a small one.
Put in a word, if I'm not mistaken, I asked for it in my last MQL cycle, it's been 4 years, but I had to listen to a hullabaloo from literate people, who said they didn't need it, just write it this way... If you want to stopprogram's execution with a critical error of access to OHLC data or indicator... i looked through half of kodobase, yes, some codewriters check these conditions, but the processing is absent, the maximum i see is the output in expert's log, like a problem happened, don't worry, i will continue to work with invalid data on this tick )))
SZY: I'm sore, I need a simple way to stop processing the current tick! - to stop working of the expert, it is possible, but to stop processing of one tick, invent and work it out - I suspect that on the level of the compiler abort() is realized not more difficult than ExpertRemove() - which already exists
ZZZY: the task of writing an EA in MQL without abort() in procedural style is more like an invention than in assembling a code from ready-made subroutines. I suspect that these constant discussions of how to write an indicator that can correctly handle history for another TF will also be easier solved using abort() - I haven't decided on this subject yet
Put in a word, if I'm not mistaken, I asked for it four years ago in my last MQL cycle. well, everything is as usual
You're right, when you start saying that, those literate people will come out of all holes, saying "this is not C++").
you need a simple way to stop processing the current tick! - it means it is possible to stop working of the EA, but to stop processing of one tick you have to invent it and work it out - I suspect that at compiler level abort() can be implemented not more complicated than ExpertRemove() - that already exists
Well, both abort and assert are implemented in the same way as in the code above. Although it's certainly ugly and sometimes confusing, because I don't always notice the preceding message in the log. Maybe there is some other error, that would return something like "internal error" in the log? At least it wouldn't look so embarrassing )
You're right, when you start saying that, those literate people will come out of all holes, saying "this is not C++").
Well, both abort and assert are implemented in the same way as in the code above. Although it's certainly ugly and sometimes confusing, because I don't always notice the preceding message in the log. Maybe there is some other error, that would return something like "internal error" in the log? At least it would not look so embarrassing )
here@Vict helped me to make an exception with exit to OS via macro substitutionhttps://www.mql5.com/ru/forum/318246/page10#comment_12651045
, in general a workable solution, but... but it looks ugly and disgusting ! )))