SP3.3

Feb 17, 2006 24 Replies

That's good! But I wonder what else will broken in 3.4, that we will have to wait for 3.5 to be fixed?!?! Sounds kind-of like a domino effect to me...

I'm thinking that sp3.2 which is the 64bit version pre-release might have integrated code that contributed to this. So there was probably a lot more behind the scens code changes than ususally for a SP. I'm speculating of course.

You may be right. But it is still very frustrating.

I personally think that they should dump the idea of integrating 64bit code into the existing program. That's asking for trouble in my opinion (which is what may have happened here). I think they should implement a totally separate 64bit version, and slowly fade-out the 32bit version over the next several years. I know this would put a lot more load on SW to maintain 2 versions,,,, or would it?!?!

My $0.02

It's my understanding that 64-bit is primarily a compiler option.

Anyhow, a more important point is that these things should have gone through EV if risky changes are being made (and evidently are).

I think it is a compiler option but some things may need optimizing to run on 64bit which may mean code changes or rewrites. And rewriting code to take more advantage of 64bit abilities will be advantageous to all eventually.

Join the Discussion

Have something to add? Share your thoughts — no account required.

Didn't find your answer?

Ask the community — no account required