Support Board

Date/Time: Sat, 27 Apr 2024 01:27:31 +0000

Post From: Notice: Study Exceptions in New Versions and Code Efficiency

[2020-05-10 22:39:35] Link To Thread - Link To Post [Go To First Post]
Sierra Chart Engineering - Posts: 104368
We had a question by email as to why the existing ACSIL persistent functions were not optimized and these new ones were created. And whether these new ones should always be used now. Yes use these fast functions from now on in most cases. The other functions are still useful for pointers and strings and when accessing persistent variables across charts and studies. And when you need to use a key value that does not fit within the index range of 0 to 10000. The older ACSIL persistent functions cannot be optimized because they support a random key value which can be in the range from zero to UINT_MAX. Whereas the fast ones specifically are using an index which needs to start at 0 and go up. Although perfectly fine to start at 1 and fine to skip indexes but you should not. The old ones use a STL map, the new ones use a STL vector. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, change to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2020-05-10 22:41:42