source control and file systems (was RE: SAA Historical perspective)

On Mon, 18 Feb 2002, Tom Daly wrote:

> Personally, I never liked the QRPGSRC, QRPGLE, QCLSRC, QDDSSRC, etc.
> method.  Just one source file for all source types.  I then group related
> items - like our APIs, others' APIs, and BagOTricks into individual source
> files.

That creates other problems.  Now you have one giant source physical files
with a huge number of members.  These members are not grouped by function
or program, but alphabetically (or by date).  Unless you have a good
naming convention who knows what goes with what?  And what is a good
naming convention?  Granted this method does solve some problems but it is
only a partial solution.

> I think having a hierarchy of directories to search for source members might
> be overkill.

Imagine this:  You have all your source in /QOpenSys/mysource.
/QOpenSys/mysource is NFS mounted on your computer.  You have a favorite
text editor (mine is emacs, j is a cool java editor, heck even notepad
would work).  You need to find all occurrences of you Super_API function
call.  So you grep (hey grep again!) for "Super_API" in your NFS mounted
source directory and open the resulting files in your favorite editor.
Maybe your editor tracks recent files so you easily jump from source file
to source file making your changes.

Or maybe just add a "Search directories recursively" option to search in
PDM.

James Rich
james@eaerich.com