Support Board
Date/Time: Thu, 01 Jan 2026 17:15:14 +0000
Post From: Understanding Sierra Chart Work to Port To Linux and Windows is Doomed
| [2025-12-31 22:58:58] |
| Sierra_Chart Engineering - Posts: 22130 |
|
It just occurred to us, that our current and previous statements regarding the use of MFC (Microsoft Foundation Classes) within Sierra Chart where/are likely misleading or could be easily misinterpreted. MFC, covers a large amount of functionality. It wraps most of the windows OS and provides data containers, classes for file I/O. Classes for working with date and times. Probably network I/O classes. Graphics classes. Certainly classes, for user interface components like windows. Classes for strings. MFC has a lot of functionality. You can see everything here: https://learn.microsoft.com/en-us/cpp/mfc/hierarchy-chart?view=msvc-170 As we look through that, Sierra Chart has used hardly/barely any of that. Sierra Chart has used definitely less than 10% of that . We have always kept the use of MFC to an absolute minimum. MFC was only used, in a limited way, because in the beginning, we needed to support OLE for a spreadsheet control we were using. Something like that. Sierra Chart has always used a very small subset of this MFC functionality. Primarily classes for user interface components like windows and dialogs. For example, we never used any of the data containers like CArray. We always use C++ STL. So really it was never fair for us to ever say or imply that Sierra Chart is an MFC program. At this time, probably about 98% of Sierra Chart is not MFC. And there are also string classes, and functionality part of the standard C++ library. For this last part regarding C++ strings and related functionality, Sierra Chart does not use any of this. In the past there was some limited use of std::string but not much. Even functions like sprintf, Sierra Chart does not use. We used to, but that was replaced about 9 years ago with higher performance, functions to convert numbers to strings. And we have our own string class we have used for more than 10 years. We may have used a MFC file class but that was eliminated, probably like about 10+ years ago. Gradually the use of MFC in Sierra Chart has become less and at this point, it is very little. The only thing remaining is some remaining dialog windows. This is all. And of course the main message loop, runs within MFC. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2025-12-31 23:02:12
|