Suggestions to MqlLock
27 views
Skip to first unread message
loopsider
May 29, 2012, 4:21:22 AM5/29/12
to MqlLock
The idea is very good! But, as a code developer, I don't like the
authomatic separation into dll and mql parts too much. For complex
codes, it will lead a) to a low efficiency (slow execution), b)
inevitable small issues of compatibility between mql and C++, and c)
difficulty in ensuring that the modified code is exactly equivalent to
the original. For my codes, I would prefer to do the separation
manually, that is to provide explicitly the part of the code to be put
into dll. This should be qiute easy to incorporate into MqlLock as an
additional feature.
authomatic separation into dll and mql parts too much. For complex
codes, it will lead a) to a low efficiency (slow execution), b)
inevitable small issues of compatibility between mql and C++, and c)
difficulty in ensuring that the modified code is exactly equivalent to
the original. For my codes, I would prefer to do the separation
manually, that is to provide explicitly the part of the code to be put
into dll. This should be qiute easy to incorporate into MqlLock as an
additional feature.
Fx1.Net
May 30, 2012, 8:36:25 AM5/30/12
to mql...@googlegroups.com
Loopsider,
thank you for your suggestion. In fact we want to offer different levels of obfuscation in near future. Right now all files are beeing converted in level7 which is (currently) highest level. Actually to speed up the EA lower levels of obfuscation can be used. We already support this but anyways compile everyone in level7 for debug reasons.
best regards
Reply all
Reply to author
Forward
0 new messages