with memcpy. That's where the pointer is passed to.
No, they can take the pointer but not the slip.
___________
Okay, so it's probably impossible to do it properly.
No, they can take the pointer but not slip it.
and slip it in, tested.
and slip it in, tested.
Show me an example.
Well, it's in the article, isn't it?
I'm trying to insert the code. The server freezes.
Well, it's in the article, isn't it?
first example
int Source is passed - essentially a memory address
and copied into the array char Dest[10]
- 2012.01.31
- o_O
- www.mql5.com
did you get it right? are you overloading memcpy for all types now?
Just don't forget that address size is long for 64 bits.
--------------
Suggestion number one: do you think we should ask developers to make a native function like long ArrayGetAddress( object array) ?
If they won't do it, suggestion two: we should push #ifdef. Renat promised to implement it.
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Motive:
The point is that quite often in turkeys you need access to timeseries, which are passed to OnCalculate.
The nesting of these functions can be quite significant, and we have to drag this array from OnCalculate throughout the call chain as a parameter.
While in a significant part of the chain this array isn't needed in the hell.
What we want:
Some semblance of an array reference, like this:
BUT. Mandatory condition - there should be no array copying.
At first glance, this may seem unrealizable. But I suspect it can be done.
What do you think, gentlemen?