Functions please ?
- This topic has 1 reply, 2 voices, and was last updated 9 months ago by
.
-
Hello @Nicolas,
6 months or so ago you mentioned that ProRealTime is working on the possibility of functions. Can you please lay out (ore ask) the roadmap of that ?
With all the numerous do’s and don’ts it has become almost impossible to apply maintenance to the existing codes. New insights occur daily (I am serious) and they almost all relate to broker issues and how to counter-attack them. Example is the new means IG will apply as per March 28 2024 (What this mail from IG mean?) and how “we” (?? OK, I do) will need to undo all sorts of provisions in the (thus numerous) codes to let work things differently (back to normal, so to speak). Again, this is just an example.
An other example I currently have at hand could be more speaking : envision a Forex system against a Future System, and you will see that both need to be very different technically. For example, when you have something (Fx) running in PRT-IG, don’t you think you will be able to run that in PRT-IB, already for the Contract Size in order with PRT-IB. Thus, adjust about all lines of code to incorporate that. Yes, but it is a general thing, and when you’re done, you can start all over when you start with Currency Futures. Again Contract Sizes, but applied very differently and different for Large vs Mini vs Miro.
And then today I am starting with Commodities. Some are Fx-like and behave similar regarding PipValue but the PipValue is different, others are more Future-like and bear their own specialties hence yet is another “group”.How does ProRealTime expect us experienced programmers to not drop dead from misery because it has become undoable to make decent Systems in a decent environment, being annoyed at it because of being experienced (I personally don’t know of any programming language that does not allow for functions or the like, also not from 50 years ago – just saying).
Please see below; the problem could be that I am doing this for real. This gets larger each day and it is not really my fault (Broker issues are). If I run into a new insight I want to apply this once and not 100+ times because I have so many codes, with specifics for all the specific situations (and which even could reside in a (sub) routine themselves);
If I need to incorporate PipValue where I previously hard-coded it (10000 for Fx systems), I simply can’t spend 20 minutes at doing it for ONE System while I have a 100+ live codes. This will only lead to error (typo’s, forget something, divide instead of multiply). And so I don’t adjust the other (running) systems which is also the most wrong thing to (not) do.Please notice that incorporating functions as functions are meant to be and behave, could be a more tough way for ProRealTime to create (also thinking about response/speed). But how easy won’t it be to make Includes which would just do the job (change the included source – recompile the main, done). And make them recursive (an Include is allowed to include).
And when you are hopefully on the job anyway, how difficult can it be to automatically have Graph(OnPrice) commands removed by the parser (the one going to ProOrder) ??
Hence why do I need to make another redundant copy of a code in order to make it Live (or for Demo for that matter) ? … we have a painful-nothing to really debug – luckily we have Graph and GraphOnPrice and Print for V12, but I need to inject that in the source and remove it again each time ? … hence the redundant copy.Maybe I am the only one who wants this to be a most serious endeavor ? The only one who likes to help PRT getting there ?
1 user thanked author for this post.
Find exclusive trading pro-tools on 
