Download find_marks User Manual - Bound

However, before the file­name sub.asm both ­com and ­pre are defined. This completes the parameters for the generic format so sub.asm is scanned with the generic mark format using a single semicolon as the comment prefix and a triple semicolon as the mark prefix. The mark suffix is not defined so no suffix is used. To make this operation clearer, it is better to write the two options together, thus:
find_marks lib.c ­com=';' ­pre=';;;' sub.asm
After both ­com and ­pre are set once it is enough to use either of them to choose the generic mark format for the following files. For example:
find_marks ­com=';' ­pre=';;;' sub.asm ­auto lib.c ­pre='#' fuu.mac
This command scans sub.asm with the generic mark format using a single semicolon as the comment prefix and a triple semicolon as the mark prefix; then it scans lib.c with the C mark format (based on ­auto and the .c suffix); and finally it scans fuu.mac with the generic mark format, still using a single semicolon as the comment prefix but now using a hash character as the mark prefix.
File­name suffix
The generic mark format is never chosen based on a file­name suffix. It can only be chosen by the options ­com and ­pre .
find_marks user manual
Writing marks in source code
13