When will it be right to upgrade to 4.x from 3.249 ?

[nurquhar]

Given the on-going discussions about various 4.x "features" and the fact that hardly a week goes by when I don't get a "new compiler update newsletter" email, when do we think 4.x will be stable ?

I am reluctant to leave the cosy frying pan of PCM 3.249 to find I am in a 4.x fire. The reason I ask is I have been using PCM since about the end of 2001 and its took years to arrive at 3.249. Should I wait about 3-4 years and try 4.x then ?

[Ttelmah]

Do what most other people do, and have both.
At the moment, I install V4, into 'PICBeta', and have this together with half a dozen older versions installed. Each new version of V4, gets a quick test, and if I have any problems, I 'trot' back to the older releases.
In general, when 'saving' code from a project, I always make a note at the start of the source file, what compiler was used, and include it in the backup archive. This way, you know where you are, when you have to go back to a project.

Best Wishes

[Douglas Kennedy]

The decision most likely hinges on what is in your best interest.
If v3.249 works for you then if it ain't broke then don't fix it. The upside for v4 must be in its new features and the downside is accepting the pit falls as the price of being ahead of others in using it. A v4 user appears to accept the role of an unpaid tester. The downside to v4 seems to have been very substantial in comparison to the downsides in moving from v3xxx to v3xxx+1.
I have yet to read of a productivity gain from using v4 that makes its early adoption warranted. Hopefully this year we will read about how it saved time and money but I rather expect that it will be the lack of support in v3 of newer chips that will drag us kicking and screaming into a v4 with its most reliable versions still ahead of us.

[asmallri]

[Darren Rook]

I have done a few projects on the 18FxxJ60 in V4 with no problems........
_________________
I came, I saw, I compiled.