To see the format required by MT4, do an export of some existing data. It will generate a file that looks like this: 2015.01.01,22:00,1.21038,1.21038,1.21037,1.21037 2015.01.01,22:01,1.21038,1.2105,1.21036,1.2105 ...

hardcode the account number in the mq4 then compile unique ex4 for each customer. I suspect you wont be able to patch the ex4 after compiling because (I'm guessing) the protection on ex4 involves some kind of signing/checksum.

Don't knock the bicycle for energy efficiency - but possibly off topic

Decompiling is a lot harder than it used to be, so they are already protected to some extent. (not 100% as MT can decode them ) For more protection: 1. Use signals - (requires infrastructure) 2. Lock code to account ID - need a process for users ...

True. I wonder if it was being overly pragmatic to get past AV without considering user perception, or if it was being deliberately malicious to make it difficult for users to prevent updates. Hanlon's razor perhaps?

What do you think their motivation for doing this is? Considering a) it's not a virus b) a couple of AV vendors are reporting false positives and not fixing them? How is above use of png in their own program heirarchy being malicious exactly?

Let's not confuse - things that are difficult because you have to be an expert coder with - things that are difficult because they have changed from what was before A novice coder new to MQL4 will not necessarily have the latter issues? They will ...

IMO people do not have to be any better coders than they were before, to use MQL in the same way as before. Most of the old stuff is pretty much supported as is. However The real problems are: 1 the build 60x releases are very buggy. ( 2. The ex4s ...

I thought new MQL4 has this? aka Strongly typed. I've certainly seen plenty of warnings regarding lack of typecasting in new MQL. Which , as you say, is a good thing.

Hi, there are two things: 1. StringSubstr is changed. EOL flag is now -1 not 0 2. NumberToStr is calling StringSubstr(str,start_pos,length) with a negative start_pos. outstr = StringSubstr(outstr,StringLen(outstr)-9-nleft,nleft+1+nright-dotadj); ...

As long as you are not modifying the array in the function just insert & in the function call. If you do happen to modify the array in the function , just make a copy inside the function and use that.

It needs someone to make a small test case. ps we now have standard functions StringTrimLeft, StringTrimRight, StringToUpper, StringToLower so replace these

You really need to just have a general idea of areas that have changed. You dont need to learn all of the new features to port existing code. Just be aware of which features affect existing code: At present main areas of change seem to be: New ...

Ignoring OOP specifically, One thing the old MQL4 really lacked (which it has now) was some kind of compound datatype (aka Structures / Records etc). Even C had these, they have been around a LONG time in programming because they are so ...

I suspect it will be possible to to a batch search and replace to fix up the majority of warnings and errors (eg variables like 'char' , 'new' etc). (skipping replacements within literal strings!) and dealing with externs etc. Then I think most of ...

Hi, following on from my previous post: The way this is being rolled out does seem a bit unprofessional by MQ. with existing indicators breaking. That should never have passed QA However, my understanding is that there is no need to learn the OO ...

So I gather MQ are not really helpful in providing clear guidance for migrating existing source to the new language? If MQ wont provide it, is it possible for the community to work together provide some clear migration steps for existing source ...

This was an old thread , and is all outdated due to new options in MT 4(build 507 + )