Visibility with throw and shared objects - c++

Question

I'm porting a code from Windows to CentOS but I'm confronting with a problem that I've never seen before.
Given that function declaration (there are many more) :
byte getValueInt8() const throw(.../*Exception*/);
I get this error:
error: expected type-specifier before ‘...’ token unsigned short getValueInt8() const throw(.../*Exception*/);
Of course I've checked the internet and I've found that it is a visibility problem in shared objects.
This website https://gcc.gnu.org/wiki/Visibility explains that but I had already done this when I read it.
My defines are:
#if defined(_MSC_VER)
#include <winsock2.h>
#ifdef MFTINTERFACE_EXPORTS
#define EXPORT_IMPORT __declspec(dllexport)
#else
#define EXPORT_IMPORT __declspec(dllimport)
#endif
#elif defined(_GCC)
#include <arpa/inet.h>
#include "CmnSocketsDef.h"
#include "CmnDefs.h"
#define EXPORT_IMPORT __attribute__((visibility("default")))
#else
#define EXPORT_IMPORT
#define IMPORT
#pragma warning Unknown dynamic link import/EXPORT_IMPORT semantics.
#endif
Of course, all EXPORT_IMPORT are well set in my code.
The code, before modification compiles in Windows.

Answer 1

throw(...) as an exception specification isn't legal c++.
I can only assume you've encountered a Microsoft abomination extension.
You'll need to remove it. In any case the only exception specifier that makes any sense in reality is nothrow (or throw() if you're using an ancient compiler).
Indeed, here's the smoking gun:
https://msdn.microsoft.com/en-us/library/wfa0edys.aspx
proposal to deprecate:
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2010/n3051.html