PureBasic Forums - English

This is based on a subject raised in this thread:
viewtopic.php?t=11258&start=0
regarding PB version numbers and the compiler v. the supporting componentry (or whatever).

I post here so as to not clutter that announcement with this.

From the post I think I can see some advantages in the way I manage my various PB releases on disk and was wondering if someone could help me work out which files belong to each other.

Eg:

When talking the compiler, what files are considered integral to a compiler release, depend on the compiler or vice-versa? Which are independent or semi-independent?

What other groupings of files are there. Eg, Lib file and associated res file.

What files absolutely must stay within a compiler release, and what might be usable with other releases.


I think I could organise my folder structures and write a small prog to have whichever configuration I want in the main development folder area. This would be based on the project I am playing with at the time.

But I am not 100% certain of which bits absolutely need which bits, etc, and which could perhaps be used with several compiler releases.

Messy post but hopefully you know what I mean and can help.

yeah, but euh... why don't you simply create a few batch files and rename your folders on the fly, if you desperately want to stay working in the same folder?

Why do you want to mix different PB versions ?

lol.

Okay, I can write a wordy dissertation and justification if you like.

It just seems to me that there may be hidden (to me) flexibility in PB method of handling things that can be utilised. But I may have read more into the post (referred to above) than was there.

However, simple example - Let us say

PB_library_X ver 1 will work with PB_compiler ver 2
.. and ..
User_library_Z relies on PB_library_X ver 1, but breaks with library ver 2

Then a mix might overcome some situations of broken libraries, etc, with releases.

Take the #PB_Any approach. Some PB libs/commands use both the indexed and dynamic approaches. Could be that an older lib will still work with a newer compiler.

Etc.

But what do I know?

Anyhow, nm, let this die if it is too far removed from reality.

be sure and include your data set if you do write a dissertation. and id like to setup a defense for the dissertation as well. heheh. just kidding. everytime i hear "dissertation" i realize my dissertation defense is about 2 1/2 yrs away for my PhD, and time is going too fast.

my opinion: any small changes to the compiler= + .01
intermediate changes= +.1
major changes= next step to whole number
changes to just the GUI of the program = +.01

Time gallops. You'll get through with flying colours.