On 2007-09-20 03:55-0700 Jerry wrote:

> What is the proper "front matter" that should appear at the top of
> the Ada examples? I haven't checked to be sure, but it seems that
> some C examples have license-related information, a copyright, and a
> statement that the example is part of PLplot, but others lack all of
> this.

Use x02a.adb as a template of what should be done.

Also, there always appears a line like this:
>
> /* $Id: x03c.c 6375 2005-10-07 17:53:37Z airwin $
>
> Should there be a similar line for the Ada examples?

Just add a "-- $Id$" string to your new examples in the same place as in
x02a.adb.  Subversion expands $Id$ appropriately when checking out (and also
unexpands $Id when storing internally in the repository).

Jerry, the comments below here do not affect you directly since I have
been committing your Ada code drops for you.

As a general note, PLplot core developers with svn write access who commit
_new_ files to our subversion repository must set the svn:keywords property
for those files where keyword expansion is desired.  Use the following
command to implement this

svn propset svn:keywords "Author Date Id Revision" filename

Also, if a developer notices that a keyword is not being expanded properly
on an _old_ file they should do the above svn command to correct the problem.
(I have just done that on some of the ada examples where I originally
forgot to set the svn:keywords property.)

Remembering to do the appropriate propset for _new_ filename patterns can be
problematic (as I have just demonstrated for Ada files :-) ) so from now on
I have automated this for myself by adding the following lines to
$HOME/.subversion/config file.

*.c = 
svn:keywords=Author;svn:keywords=Date;svn:keywords=Id;svn:keywords=Revision
*.h = 
svn:keywords=Author;svn:keywords=Date;svn:keywords=Id;svn:keywords=Revision
*.cc = 
svn:keywords=Author;svn:keywords=Date;svn:keywords=Id;svn:keywords=Revision
*.cpp = 
svn:keywords=Author;svn:keywords=Date;svn:keywords=Id;svn:keywords=Revision
*.f = 
svn:keywords=Author;svn:keywords=Date;svn:keywords=Id;svn:keywords=Revision
*.fm4 = 
svn:keywords=Author;svn:keywords=Date;svn:keywords=Id;svn:keywords=Revision
*.f90 = 
svn:keywords=Author;svn:keywords=Date;svn:keywords=Id;svn:keywords=Revision
*.java = 
svn:keywords=Author;svn:keywords=Date;svn:keywords=Id;svn:keywords=Revision
*.py = 
svn:keywords=Author;svn:keywords=Date;svn:keywords=Id;svn:keywords=Revision
*.adb = 
svn:keywords=Author;svn:keywords=Date;svn:keywords=Id;svn:keywords=Revision
*.m = 
svn:keywords=Author;svn:keywords=Date;svn:keywords=Id;svn:keywords=Revision
*.tcl = 
svn:keywords=Author;svn:keywords=Date;svn:keywords=Id;svn:keywords=Revision
*.sh = 
svn:keywords=Author;svn:keywords=Date;svn:keywords=Id;svn:keywords=Revision

Those with commit access to our svn repository will probably want to do the
same. I believe these patterns cover most of the various source code files
we might add to our repository, but if there are more (for example if we
start adding perl examples where we might want keyword expansion) it is easy
to add the appropriate suffix.

(N.B. I have been specific about suffixes here rather than specifying a *
wildcard to apply the property to all new files because for certain files
[e.g. binary files] you do not want keyword expansion.)

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation
for stellar interiors (freeeos.sf.net); PLplot scientific plotting software
package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Plplot-devel mailing list
Plplot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plplot-devel

Reply via email to