New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ModelicaStandardTables: Avoid C++ implementation for shared table arrays #1550
Comments
Comment by beutlich on 7 Aug 2014 08:06 UTC Martin (S.): Can you please define TABLE_SHARE in OMC to test it. I already did compile tests with GCC on Linux (where Posix threads are available) and MinGW (where it falls back to the _WIN32 branch). ToDo: Should we rename uthash and gconstructor headers to avoid name clashes? At least we should mention them in the license exclusions of MSL. |
Comment by sjoelund.se on 7 Aug 2014 09:06 UTC (I am unsure why we would need the gconstructor stuff; if it is for FMU's, tools should anyway terminate the simulation which means we can reference count the external objects and free the main hash table. It does no harm as it is though.) |
Comment by beutlich on 7 Aug 2014 09:20 UTC License info is fixed in 3cd32ed. The gconstructor stuff is required to have a module-wide initialization call of InitializeCriticalSection and finalization call of DeleteCriticalSection on Win. See also http://stackoverflow.com/questions/1113409/attribute-constructor-equivalent-in-vc. |
Modified by beutlich on 7 Aug 2014 09:24 UTC |
Changelog modified by beutlich on 7 Aug 2014 09:24 UTC |
Comment by beutlich on 7 Aug 2014 11:15 UTC |
Reported by beutlich on 7 Aug 2014 07:28 UTC
In #1110 a C++ implementation supporting common/shared table arrays (i.e. same table from same file referenced by multiple table objects) was committed. Actually C++ was used for two reasons
In Get rid of static buffer in ModelicaInternal #1433 we discussed that the C++ layer actually can be avoided.
Migrated-From: https://trac.modelica.org/Modelica/ticket/1550
The text was updated successfully, but these errors were encountered: