The WRITE issue will always cause a compile error. There are no "silent" bugs in PBP 2.60 as far as I know. If you get a successful compile, you should be ok.

I felt the same pain as Joe, at first. All of our sample programs had to be edited to change the "loop" label. I remember questioning the wisdom of making LOOP a reserved word, given that our published examples had used the word as a label for so many years. In the end, after much consideration, it was decided that the utility of the DO..LOOP structure would be worth the effort for the majority of users.

The fact that 2.50C could easily be maintained alongside 2.60 was a factor in the decision. It seems that this capability should be made more apparent. I'll try to remedy this. Our policy has always been to never force users to upgrade and to always allow versions to coexist.

This seems like a good spot to point out that users should always run the latest patch for their version of PBP. We release patches when we feel that the number of fixes warrants it. The reason there were A, B, and C patches for 2.50 is because we found issues that we felt obligated to fix. Version 2.50 was a major change in PBP and it took a while for the fallout to settle. If you continue to use version 2.50, I highly recommend that you go to our site and download the 2.50C patch.

http://melabs.com/support/patches.htm

Ioannis is correct about the manual. Sometimes it seems like the thieves have our latest version before I do. We have resisted license keys and registration servers for a long time, but I don't know if we can hold out much longer. It may be that the inconvenience of a required registration would be offset by other conveniences that it would allow, like a downloadable manual. I would like to thank all of you who have resisted the temptation to share illegally and encouraged others to purchase a legal copy. PBP would not exist if it weren't for so many honorable users.