changing throw(...) changes interface?

[Daniel Etzold]

Hi,

does adding a throw(...) or throw() to a method or just changing
the number of exceptions listed within a throw change the
interface?

Example: having a class with a method within a class library
class x {
....
void f()
[or void f() throw( int )]
};

and changing it to
class x { ...
void f() throw() [or throw( int ) and so on]
[or void f() throw( int, char*) respectively]
};

will the library still be binary compatible?

Regards,
Daniel

 

[Victor Bazarov]

does adding a throw(...) or throw() to a method or just changing
the number of exceptions listed within a throw change the
interface?

No, but it changes the type ("signature").

Example: having a class with a method within a class library
class x {
...
void f()
[or void f() throw( int )]
};

and changing it to
class x { ...
void f() throw() [or throw( int ) and so on]
[or void f() throw( int, char*) respectively]
};

will the library still be binary compatible?

Binary compatibility is beyond the scope of comp.lang.c++. You
should ask in the newsgroup for your compiler.

V

 

[Daniel Etzold]

Daniel Etzold wrote:


Binary compatibility is beyond the scope of comp.lang.c++. You
should ask in the newsgroup for your compiler.

I'm using GCC in various versions.

 

[Victor Bazarov]

I'm using GCC in various versions.

Then you should consider posting to 'gnu.g++.help' or go to their
web site and find where they hang out.