| 1 |
> 3.2 is labeled by GNU to be 100% multi-vender compliant with the C++ ABI |
| 2 |
> now. Which is the core prob with the new gcc releases. By skipping |
| 3 |
> straight to 3.2 we'll avoid 2 problem transitions.. 1 from 2.95 to 3.1 |
| 4 |
> and then from 3.1/3.1.1 to 3.2 instead we'll have 2.95 to 3.2. |
| 5 |
|
| 6 |
The GCC Page (http://gcc.gnu.org/gcc-3.2/changes.html) says it is MultiVendor V3 |
| 7 |
compatible - does that mean that it's compatible (again) with 2.95? There |
| 8 |
aren't any other changes listed on the page, so does that also mean that no |
| 9 |
changes in code are required from 3.1 to 3.2 to compile? Will this just mean |
| 10 |
going from 2.95 to 3.2 will be a matter of fixing the ISO C/C++ standards, just |
| 11 |
as for going from 2.95 to 3.0? |
| 12 |
|
| 13 |
|
| 14 |
|
| 15 |
mjt |
| 16 |
--------------------------------------------------- |
| 17 |
Matthew J. Turk <m-turk@×××.edu> ICQ: 3856787 |
| 18 |
"Music is the Best." - FZ thecatfishman.org |
| 19 |
http://pubweb.nwu.edu/~mjt631/spamoff.htm |
Archives