PureBasic Forums - English

While we are waiting for the much anticipated stable release of PB 4.6, I was wondering if there would be any drawbacks in using the beta version to build our projects for release. Since compilers only "translate" the functions that we use in our code, is it fair to say that buggy functions that are not called would not affect our projects?

I'm particularly interested in the CanvasGadget.

Oh, I wouldn't use it. There could also appear bugs in functions that always existed and worked fine, although the chances are low. Mostly new commands need some work... see all the 3D function bugs being reported... Anyway, I think I remember something special with arrays being broken in 4.60 Beta X.

So I wouldn't use it for compiling your final executable. But testing your code with it is always fine, because only that way bugs can be found and fixed.


By the way: 2 month for beta 3 ??

Never, never, never, never, never, ..., never use an unstable version of the compiler to create your release version

By the way, there was a "small" bug in a RC version of python or something. In this pre-release the uninstall script deletes the whole /usr/ directory on linux

If your program is tested and working with beta 3 I don't see any reason not to use it.

If problems occur and it's revealed a beta was used legalities maybe a reality.
We never use anything other than a known stable release of anything.
Even in OS's we always wait for the first SP before implementation.
Call us paranoid , I know ...

If your program is tested and working with beta 3 I don't see any reason not to use it.

Agreed. Thorough testing is the key. If you're happy with the stability and performance of your release candidate, it really doesn't matter what you compiled it with. As far as the CanvasGadget goes, while it might benefit from some additions to its functionality, what's there seems quite solid. I haven't been able to break it anyway.

Trond wrote:If your program is tested and working with beta 3 I don't see any reason not to use it.

I agree with this. Code is code. It doesn't magically "change" or stop working properly just because you publically released your app. In other words, if your app is working fine and as expected with the beta, then it'll also work fine for the public.

The canvas gadget is fine, it's been given a good thrashing by a few of us.
Though you never know if it's going to get changed in the next beta or if the change could introduce a bug.
Just make sure you isolate the current PB version just in case!

Thanks for all the input - some good points to consider.

Have you done unit testing with PureUnit?