3 Apr
2008
3 Apr
'08
9:38 a.m.
Dear Alexei, Alexei Sheplyakov wrote:
* Add a function that re-establishes binary compatibility but don't expose it in the public header file.
I'm afraid this will make CLN unsafe to compile with -O2 again.
I don't think so. It would make the two functions unsafe. But these functions can be used only by programs compiled against CLN-1.2.0. Programs compiled using CLN-1.2.1 are safe anyway as the bad signature doesn't exist and programs compiled using CLN-1.2.2 are safe because the bad signature is not exposed and, hence, not used. -richy. -- Richard B. Kreckel <http://www.ginac.de/~kreckel/>