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
comp.lang.fortran
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
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 5 2010, 1:12 am
Newsgroups: comp.lang.fortran
From: glen herrmannsfeldt <g...@ugcs.caltech.edu>
Date: Tue, 5 Oct 2010 05:12:18 +0000 (UTC)
Local: Tues, Oct 5 2010 1:12 am
Subject: Re: An interesting way of keeping track of versions
Print | View thread | Show original | Report this message | Find messages by this author

analys...@hotmail.com <analys...@hotmail.com> wrote:
> On Oct 4, 8:41 pm, dpb <n...@non.net> wrote:
>> analys...@hotmail.com wrote:
>> > ... and as long as the output and source (as a diff
>> > against a base version) are printed out permanently together, you have
>> > a track of what you did effortlessly.

(snip)

> everybody seems determined to miss the point.
> Yes there are source code control systems.
> yes you can write a version number into images of your source.
> But version of program output are separate objects from versions of
> the source code - the room for human error comes in when you somehow
> forget how you produced one version of the output.  The proposed
> method ties program output to source-code automatically and briefly  -
> in many case, the source-code diff output would only be a few lines
> which would be difficult to recover otherise if you have been
> tinkering a lot.

If your changes work such that differences to a base version are
all you need, and small enough, then yes.  Though you can do better
than that.  With make you could automate the diff, then generate
Fortran source containing the program text as literal constants.
Then the diff lines would be compiled in, and stay right even if
you changed the source, or copied the executable to another computer.

> The only human effort comes in to use the diff output to convert the
> base source-version into the one you want - but you have the program
> output to help make sure that the job is done correctly.

If you have N different versions, then there are N*(N-1)/2
possible diff outputs.  CVS and SVN will generate those for you
with a very simple command, given the version numbers.

Also, with one command they will give you the source files as
they existed for any version, but still not forget all the other
versions.

-- 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.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google