Question on arrays
Forums › ProRealTime English forum › ProRealTime platform support › Question on arrays
- This topic has 3 replies, 2 voices, and was last updated 8 years ago by Wing.
-
-
10/27/2016 at 7:56 PM #15652
Hello everybody,
I am going to write in English and not German, since most people come from different countries, and English is universal language.
To my german fellows, of course, go ahead and ask me in german.
Well, I haven’t found anything on array ‘s when reading the german Prorealtime-programing-Book, so I wanted to know if anybody could
in short, though comprehensible way, explain with an practical example how to create, fill and read an array in Prorealtime.
I’d really appreciate that …
Thanks Tom.
10/27/2016 at 11:24 PM #1565510/28/2016 at 4:33 PM #15677Thanks wing. Oh man, I have to confess that really sucks!( Sorry for my bad language.) Why is this?
As you said wing, high, low, close, open are also arrays and it is so easy to fetch a point in the past. We all see it when using them … high[34] = high[78] … two points easy compared.
It is all about fetching a defined point in the past and working with these points.
It could be any point, a fraktal high …or …. if high[3]<high[2] and low[2]>low[3] … you name it.
Is it so difficult to program Arrays into existence? I mean, arrays are so useful, and to finally answer your question, in my case I want to use high and low-fraktal points and compare them
with other high and low-fraktal points, or use math on them. But there would be plenty of other points I would be using if I could, believe me!
Yet, it is a huge act doing this by using different functions etc. … you need counters, because you have to count everything from your last candle to get this and that high etc. …. and I haven’t been able
to do this with the complete data series … you just can’t save a point in this elegant way an array is doing it. Well, actually you can’t save points in the past at all, because on the next
candle, when your defined point appears, the old point gets lost. That’s the core problem. So you always have to count … and count … and count … and count …
Right now, I can only fetch a certain amount of points in the past, yet which I have to define previously. Means, I EVEN have to know IN ADVANCE, how many points I am going to use, because once you
put a variable in existence you have to use it otherwise you get an error. All of this is a lot of work and doesn’t even catch up close to arrays, where you just write one word. And that is really killing me, because
I am not able to transfer my different trading ideas into reality.
Well, can at least anybody tell me if there are going to be arrays in the near future? That would be great to know. And if yes, when would that be; timeframe. I really need them badly.
Thanks
10/29/2016 at 2:54 AM #15693You’re right, not being able to use arrays is very limiting in programming anything.
I suspect the reason arrays are not available, is to save CPU power on ProRealTime servers. Each system/indicator running is already running through an array (the candles), when adding arrays on top of that, people create powerful but CPU-intensive systems that check many 1000’s of data points in an array for every candle. However, not letting us create small arrays (like max 200 data points) is a joke.
This is also the reason I think they have limits on the amount of times you can run WHILE and FOR loops per candle, depending on the amount of operations contained therein.
Arrays allow for very smart systems. Other wanted features available in PRT manual trading are sometimes not available in the system creation either, such as arbitrage-based systems.
-
AuthorPosts
Find exclusive trading pro-tools on