home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware Overload
/
ShartewareOverload.cdr
/
wp
/
bmacs.zip
/
READ_ME
< prev
next >
Wrap
Text File
|
1987-04-12
|
3KB
|
84 lines
;**************************************************************************;
;* *;
;* DONATED TO PUBLIC DOMAIN *;
;* Multifile Editing `tag' support *;
;* Version 1.0 - April 12, 1987 *;
;* Richard O. Parker - CIS: 76556, 1132 *;
;* *;
;**************************************************************************;
This archive contains three files:
1) tags.exe Creates a `tags' file consisting of
a) function or macro names
b) filenames
c) search-patterns
for editing multiple `.m' or `.c' files in
a single directory using BRIEF.
2) tag.m A BRIEF macro which implements searching
the `tags' file for a function-name (or
macro-name), editing the corresponding
file and positioning the cursor at the
beginning of the named function.
3) tag.cm Compiled version of `tag.m'.
The `tags' and `tag' facility are nearly identical to the corresponding
capability under Unix, using the `vi' editor---and I implemented this to
add to the `vi' macros for that purpose.
The `tags' program takes the following command-line:
tags [-t] [-f <tag file>] filename.[mc] ...
The `-t' flag allows for generation of tags for `typedef' statements in `C',
while the `-f <tag file>' option allows you to generate a `tags' file with
a different name than `tags'---although, `tag.m' doesn't recognize anything
except `tags'.
To use the facility, at the DOS prompt, enter the command to generate your
`tags' file. For example, if you are editing a bunch of `C' programs, enter
tags *.c
and a `tags' file will be built to address all of the `C' functions in all
of the modules. Since `main()' functions may occur in more than one module,
the tag generated for these is composed of the letter `M', followed by the
name of the module. For example, if you have a module called `test.c', the
`main()' function will be tagged as `Mtest'. All other functions are tagged
with their actual names.
Then, edit one of your files and invoke the `tag' macro, which will prompt
for a ``tag-name'' as follows:
tag:
At the prompt, enter the name of one of your functions, e.g.:
tag: generate_code
The `tag' macro will search the `tags' file for this function-name and
automatically edit the corresponding file, positioning the cursor at the
beginning of the function. If the function-name isn't present in the `tags'
file you will be notified of that fact.
You may choose to integrate this function with your favorite keyboard
emulation and have an automatic way of jumping from function to function
in your program-files. To test this macro, I assigned it to the ALT-T
key and you may decide to integrate the macro in a similar fashion.
If you have any suggestions for improvement of performance or correction of
errors, please let me know. This is my first ``commercial'' BRIEF macro
and I probably have a lot to learn. If you notice an error in generation
of tags with `tags.exe', also let me know and I'll correct it.
Enjoy!
Rich Parker
CIS 76556,1132