Support Board
Date/Time: Wed, 15 Jan 2025 13:35:42 +0000
compilation issues w/ SCString
View Count: 957
| [2017-06-16 09:00:14] |
| jizzary - Posts: 177 |
|
Hi i'm using VS community 2017 version the compiler reports the following issues ... can u pls clean it ? <....>\inc\SCString.h(490): warning C4267: '=': conversion from 'size_t' to 'unsigned int', possible loss of data <....>\inc\SCString.h(512): warning C4267: '=': conversion from 'size_t' to 'unsigned int', possible loss of data <....>\inc\SCString.h(531): warning C4267: '=': conversion from 'size_t' to 'int', possible loss of data <....>\inc\SCString.h(585): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data <....>\inc\SCString.h(586): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data <....>\inc\SCString.h(618): warning C4267: 'return': conversion from 'size_t' to 'int', possible loss of data <....>\inc\SCString.h(660): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data <....>\inc\SCString.h(681): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data <....>\inc\SCString.h(763): warning C4267: 'initializing': conversion from 'size_t' to 'int', possible loss of data <....>\inc\SCString.h(763): warning C4267: 'initializing': conversion from 'size_t' to 'const int', possible loss of data i acn do it either ... however on next version it may be overwritten so i think it should be done at yr end many tnx, shuky |
| [2017-06-16 16:34:17] |
| |
|
We do not see these warnings. Looks like you might be compiling the custom study with 64 bit addressing.
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 |
| [2017-06-16 22:41:29] |
| jizzary - Posts: 177 |
|
correct ... I did have a 64 bit compilation process but switched back to 32 (as i understood that Sierra is 32 bits) still - there are code issues that better be corrected but this is definitely yr decision ------------------------------------------------------------ BTW - when will Sierra switch to 64 bits code ? |
| [2017-06-16 22:45:54] |
| |
|
There is no need for Sierra Chart to run with 64 bit addressing. It will cause so many consequences it is not worth considering at this time. Including numerous complaints from users, even including yourself, which relate to compatibility problems. 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: 2017-06-16 23:04:55
|
| [2017-06-19 09:01:43] |
| jizzary - Posts: 177 |
|
moving to 64 bits will improve performance but most of all it will not block yr users from using 64 bit libraries the time will come where 32 bit libraries will be rare and not updated so it will beecome a MUST to shift to 64 b you are right by saying that much work is involved but the way i see it - eventually it will become a MUST tnx |
To post a message in this thread, you need to log in with your Sierra Chart account: