Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!ncar!boulder!jones
From: jones@boulder.Colorado.EDU (Mike Jones)
Newsgroups: comp.lang.idl-pvwave
Subject: Re: Call for volunteer anomyous FTP site
Message-ID: <24608@boulder.Colorado.EDU>
Date: 10 Aug 90 17:34:59 GMT
References: <6184@aplcen.apl.jhu.edu> <221@locke.water.ca.gov>
Sender: news@boulder.Colorado.EDU
Reply-To: jones@crash.Colorado.EDU (Mike Jones)
Organization: University of Colorado, Boulder
Lines: 27

In article <221@locke.water.ca.gov> rfinch@caldwr.water.ca.gov (Ralph Finch) writes:
>In article <6184@aplcen.apl.jhu.edu> gotwols@warper.jhuapl.edu (Bruce Gotwols) writes:
>>	The first step is to agree on documentation requirements.  That can 
>>be discussed here and I will summarize after a while.
>
>I think that IDL/Wave have some sort of standard already for
>user-library functions, right?  If so, would that serve for us?  Does
>anybody know what that standard is?
>-- 
>Ralph Finch			916-445-0088
>rfinch@water.ca.gov		...ucbvax!ucdavis!caldwr!rfinch
>Any opinions expressed are my own; they do not represent the DWR

That's right. We should make the documentation compatable with
the doc_library routine. The best way to do that is to fill out the library
template. On my (Wave on DS3100) Ultrix system that is in
/usr/local/lib/wave/lib/template.  On a VMS machine use 
lib/extr/out=template.pro wave$library

On my VMS version, doc_library,'template' will give the template form.
Don't just use the output of doc_library as the template, it strips the
;+ and ;- delimiters that are needed. Suprisingly the Ultrix call can't 
find the template file, but as I mentioned it is in the distribution kit. 

I've used this template for 5 years in IDL and Wave and find it quite 
useful, even for my own projects when I don't expect anyone else to 
read the code.