Compiler version control

[paulr]

Hi all,

PB is great and it improves with every version. And sometimes those improvements necessitate messing with the way old commands work, which is cool with me, as the changes always make sense. However it's heartbreaking when you want to run an old bit of code, or an example on the forum, and you find it no longer works without a long list of modifications.

How about a system where you can type in something along the lines of:

Code: Select all

#PB_Compiler_Version = 3.92

at the start of your code, and then it would always compile using the correct version of the compiler? I know there's a translator program, but converting a program is time consuming and often involves tweaking it by hand.

What do you think? Keep up the good work, PB crew.

[Mistrel]

That's a very interesting proposition however it's not just the compiler but also the libraries that define a particular release. Something like this wouldn't be possible.

[paulr]

Thanks for the response Mistrel but I think you're giving in too easily! Looking in my PB directory there are 4 folders I presume to be involved in the compilation process: Compilers, PureLibraries, Resitents, SubSystems. Between them they're about 18Mb. I'd happily devote that much disk space to every former PB version if it meant my old programs would always work.

And I think it'd be a real selling point... I think PB's awesome but I've never come across anyone else (except on this forum!) who uses it. I think it would do wonders for PB's credibility among software professionals if they know the code they write this year will still work next year and forever.

[Trond]

They don't have to upgrade. They can just keep all their PB installations and compile with the correct compiler.

[paulr]

True, but I think a better system would be one that just works, by itself, every time, wouldn't you agree?