In article <89oubf$373$1 at mach.vub.ac.be>, gbottu at bigben.vub.ac.be (Guy Bottu) writes:
>The problem with the "mark" files reported by David Mathog does not just
>occur with GCG 8 but also with GCG 10. That nobody noticed it is of
>course because the GCG mark files lay unused in a dusty corner :-)
Quite true. I dusted it off and reused that code in our hacked up REFORMAT
program, which has an option
/GAPs=file.mrk Write "." over ranges read from a gap file, which is
formatted like a GCG "mark" file. If no extension is
specified it defaults to ".mrk"
The user tried to make a second mark file from an existing one by commenting
out some ranges, and that turned up this bug.
mathog at seqaxp.bio.caltech.edu
Manager, sequence analysis facility, biology division, Caltech