| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 761.1 | Re: bcs header filenames | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Thu Jun 02 1994 13:26 | 13 |
| Date Of Receipt: 26-MAY-1994 15:50:36.19
From: SEAN::davidson "D. Sean Davidson"
To: [email protected], [email protected]
CC:
Subj: Re: bcs header filenames
I think that this is based on the file type after the dot. So for *.c files
you get a c programming header, for *.sh files you get a shell comment header,
for *.man you get a man page comment header, ...
Sean
|
| 761.2 | Re: bcs header filenames | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Thu Jun 02 1994 13:51 | 24 |
| Date Of Receipt: 26-MAY-1994 16:42:53.94
From: WASTED::"[email protected]" "26-May-1994 1342"
To: D. Sean Davidson <[email protected]>
CC: [email protected]
Subj: Re: bcs header filenames
) I think that this is based on the file type after the dot. So for *.c files
) you get a c programming header, for *.sh files you get a shell comment header,
) for *.man you get a man page comment header, ...
Ok, files with .blah extensions seem to work like that, but there's
also README files which get headers, so apparently the whole filename
can match, and a header is still placed in the file.
So, my question is: are "total filename matching" and ".blah matching"
the only two successful ways to match files for header purposes? Or
could a partial match---say everything to the right of the string
"header" in the header filename---work as well. (It doesn't seem to.)
Thanks much,
--steve
|
| 761.3 | Re: bcs header filenames | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Thu Jun 02 1994 14:06 | 18 |
| Date Of Receipt: 26-MAY-1994 16:49:51.97
From: SEAN::davidson "D. Sean Davidson"
To: [email protected], [email protected]
CC: [email protected]
Subj: Re: bcs header filenames
bcreate only matches on the WHOLE filename or the .suffix. If you look in
/usr/sde/ode2.0/tools/headers you will find files Makefile, README, USAGE, ...
The bcreate command can look in an alternate directory for matching headers
by setting the BCSHEADERS environment variable. In that directory you could
have the exact file name that matches the one to check in.
Normally the .suffix is used to identify the file and when it gets installed
the .suffix is dropped off.
Sean
|
| 761.4 | Re: bcs header filenames | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Thu Jun 02 1994 16:07 | 23 |
| Date Of Receipt: 27-MAY-1994 10:33:08.32
From: WASTED::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: [email protected], [email protected]
CC:
Subj: Re: bcs header filenames
Here's how it works. The files in the BCSHEADERS directory are
of two forms: "filename" or "header.extension". If your actual
filename is an exact match, like Makefile, or if it matches the
extension, like foobar.c (matches header.c), then bcreate will
use this. Once the file's created, however, you can set the
comment leader to anything, and put in the appropriate header:
i.e.
bcreate some-script
bcs -c"# " some-script
in the editor put /usr/sde/osf1/headers/header.sh
at the top of some-script
(default BCSHEADERS = /usr/sde/ode2.0/tools/headers)
Hope this tells you what you need to know... -josh
|