No problem Yury, Yes, if I remember correctly the problem here was with some compilers which warned about the declaration of a deprecated method, which meant we wanted to both mark it as deprecated

Classification: For internal use only Hey Damian, OK, thank you for clarification. The reason why I thought that deprecation warnings should be deleted automatically (after defining MAMA_DLL and

Hey Yury, I'm not sure the behaviour you're describing is an issue - the purpose of the pragma's is to allow you to use 'deprecated' features of the API without generating warnings, rather than

Classification: Public Hi team, Is MAMAIgnoreDeprecatedOpen supposed to work for Linux with gcc > 4.6? See the following example: // Next 3 lines were copied from wombat/.../linux/port.h _Pragma

Hi All: I’ve completed a draft version of my latest article on static analysis, using clang and cppcheck on the OpenMAMA code. It can be found at: http://btorpey.github.io/lots-o-static/ I’m

Classification:Public My feedback: Why was extending the existing MamaTransport Callback interface not considered as an approach? All sources are available only in the context of a Mama

Some changes have just been added to the origin/next branch! [Frank Quinn] Added C# generated files to gitignore .gitignore[Frank Quinn] Fixed build for C# unit

I have some feedback about the RFC for OpenMAMA Source Discovery page: https://openmama.github.io/openmama_rfc_source_discovery.html# I’m pretty much in agreement with delivering the source

Some changes have just been added to the origin/next branch! [noreply] Updated documentation for timedDispatch

Some changes have just been added to the origin/next branch! [fquinn.ni] Fixed Unittest Failures (#323) mama/c_cpp/src/c/plugin.c Results for OpenMAMA_Snapshot_Linux CI run with latest changes: CI

For Visual Studio, it appears as though the support lifecycle model changed after VS 2010. While VS2012 and VS2013 are already EOL, VS2008 and VS2010 are still on extended support. If the intent is

The question of support for visual studio is one for the community which I'll actually pose on a separate thread with its own subject so that people might read it, but since VS2013 only went EOL from

Some changes have just been added to the origin/next branch! [Frank Quinn] Revert "MAMA: Moved background thread destroy to stop (#326)" mama/c_cpp/src/c/mama.c Results for OpenMAMA_Snapshot_Linux

Hi Yury, I did have this proposed change merged, but have since discovered that it causes a deadlock in our unit test on windows. On closer inspection, it looks like the problem is caused by the fact

Hi Damian: Thanks for the feedback. I’ve made some comments below. Regards, Bill Right now, getting static analysis working with other tools is somewhat dependent on the build tooling. I use a

Hey Bill, Great to get your feedback here, and welcome to the dev list. Absolutely the right place for this sort of discussion - GitHub is I think are more geared towards individual issues rather

Hi all: I've been working with OpenMAMA for a little while now as part of my "day job", and I've also been working with static analysis tools for some time, so I thought it would be fun to put the

Hi Folks, We have a new RFC contributed by Arcontech to cover the upcoming Source Discovery functionality. Thanks very much to the Arcontech folks for taking the time to put this together. You can

Some changes have just been added to the origin/next branch! [noreply] Microsoft Visual Studio Warning Cull

Classification:Public Thanks Frank – very useful links.