Code Versioning

[ChrisVirides]

This is directed mostly at Craig and Nick but if anyone has input great.

Do you guys use any code versioning on your afl code?
For those who do not know what versioning is, its software that allows you to keep versions of code that you run, and compare it against previous versions.

[Anonymous]

Paul Leavitt wrote:

This is directed mostly at Craig and Nick but if anyone has input great.

Do you guys use any code versioning on your afl code?
For those who do not know what versioning is, its software that allows you to keep versions of code that you run, and compare it against previous versions.

Hi Paul. I have used CVS in the past but that was for more significant coding projects… In my opinion the code I have been writing is easy to compare the important parts of the code between files at a glance. Julian’s system is probably more than good enough for my purposes.

The other thing I do is use #include statements to import parts of the code that don’t change between different versions ie: database price, volume, index and gap filters. This helps to cut down on potential problems with small changes that could accidently appear.

[TrentRothall]

Thats cool Darryl!

Does it matter where you have the files saved when you are wanting to include them?

[LeeDanello]

It goes in the AMIBROKER include folder

[TrentRothall]

Thanks Maurice, that would make sense. I looked AFTER i asked.

Cheers

[ChrisVirides]

Thanks for that tip Darryl, that makes your code less cluttered.

[Stephen James]

Paul – We don’t, but just use different versions – e.g. 1.1, 1.2 etc. I like Darryl’s idea though..

[SaidBitar]

Regarding versioning i use similar to what Craig described but i add one more digit so it is 1.0.0 and the increments are based on the following:
Major i increment the digit to the left
Minor increment the digit in the middle
modification increment the digit to the right

this is what mainly is used in programming, the funny thing that after some time you will end up with huge pile of versions that are useless mainly the ones that has changes on the right digit (mainly due to mistakes) so to be honest i do not know anyway of doing this properly without lots of clutter.

recently i was thinking of keeping the most recent version and delete all the remaining and just to keep good documentation for the strategy with the modifications and their impact and why i moved from 1.0.0 to 2.0.0 and the other details regarding the performance. there are two ways to do it soft copies you can use any software from MS Word, evernote, MS Onenote, .. huge list so you can attach your old afl files and performance files over there and delete them from your hard disc.

the other option is hard copies.

honestly i am lazy to do both

[Author]

Posts