The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
From: glen herrmannsfeldt <g...@ugcs.caltech.edu>
Date: Mon, 4 Oct 2010 10:43:57 +0000 (UTC)
Local: Mon, Oct 4 2010 6:43 am
Subject: Re: An interesting way of keeping track of versions
>> If you use a version system like CVS or SVN, then you can arrangeWhile such version systems are pretty much necessary for large
>> for the version numbers to be included in the code. You can then
>> print them out when the program runs. Such systems also allow you
>> to retrieve the source of any previous version easily, or to
>> look at the differences between them (like the unix diff command).
> I should have mentioned, I was talking about one person tinkering, not
> a formal setting where the programmer has to sign in blood for code
> changes and countless higher ups would have to sign off and the
> executable/script changes actually being made by other minions, with
> pre-set fallback procedures (and of course the 3 a.m. phone call to
> the programmer).
programming projects, they are still useful for one person.
> Th only discipline needed is not to leave changes in the source codeHow do you keep track of all the changes, such that you can
> without compilation. Otherwise once the diffing code for the current
> version and a base version is written, the "tinker, run, observe
> output" cycle can proceed totally naturally with fallback to any
> version being possible with very little effort.
get back to a previous one? Comment out the old lines?
Preprocessor #ifder? A stack of listings of old versions?
Yes it is possible, and pretty often I do it that way, but
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.