Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion An interesting way of keeping track of versions
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:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
glen herrmannsfeldt  
View profile  
 More options Oct 4 2010, 6:43 am
Newsgroups: comp.lang.fortran
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
analys...@hotmail.com <analys...@hotmail.com> wrote:

(snip, I wrote)

>> If you use a version system like CVS or SVN, then you can arrange
>> 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).

While such version systems are pretty much necessary for large
programming projects, they are still useful for one person.

> Th only discipline needed is not to leave changes in the source code
> 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.

How do you keep track of all the changes, such that you can
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
it is still something that computers are better at doing
than people are.

-- glen


 
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.