GW> 1) Saveing the path information isn't difficult, but as it is stored
GW>    togther with the file name in a header line and there are no checks
GW>    on header line lengths it can create header lines that are longer
GW>    than the specified maximum line length.
GW>
GW>    I suspect this is not acceptable, views please.

idea: continue the header with the '\' character if it overflows.

begin file only occurrs after begin part or end file... maybe that can be
exploited to simplify the processing needed to support the above. either that
or process the continuation of lines before scaning for header lines.

GW> 2) Saveing the path information as Jasen has means the files are not
GW>    compatible with older versions of CSPLIT if the source files were
GW>    not in the current directory.

that was a mistake... I didn't intend it to do that. it must have crept in
while I was adding support for '/' in filenames to be treated the same as '\'
is under dos.

yeah, it was a mistake, I missed one instance of strchr when converting
strrchrs for "posix path compatability"....

***** At line number 1149
***** delete 2 lines:
      if ((NULL != (sptr = strrchr (cur->srcfile, '/'))) ||
          (NULL != (sptr = strrchr (cur->srcfile, ':')))) /* Darin McBride */
***** and insert the following 1 line.
      if (NULL != (sptr = strrchrs(cur->srcfile,":/\\"))) /*
Darin McBride */
*****

actually, I don't understand how his bit of code ever worked, I may have
replaced something tricky with something brutal:)

possibly somewhere he was changing \ into / but I seem to have broken that.

                        

--- EzyQwk V1.20 01fa018d