Hi Paul



 RM> ..., I then compiled it using Borland's dpmi

 RM> extensions, then used the debugger to find the main problem - the

 RM> line



 RM> fprintf (output, "%.*s", e_lab - s_lab, s_lab);



 PE> But this does not solve the problem with the executable that comes in

 PE> indentpe.zip, on your system.  That is still unresolved, yeah?



Correct. I gave up.



 RM> Borland's fprintf wants an int as the third parameter, not the long

 RM> int that the pointer subtraction supplied. Changing the line (and a

 RM> related line or two) to



 RM> fprintf (output, "%.*s", (int)(e_lab - s_lab), s_lab);



 PE> Yes, that is correct, the first version was buggy.



 PE> Ok, so can you tell me again what is the total (and minimal) of the changes

 PE> you had to make to make the source code work with Borland? So long as they

 PE> aren't dirty global changes, I'd like to modify my version so that it works

 PE> with Borland.



Ok, but it may take a week or two to tidy it up. I'll try to get

the warning list below 50 while I'm at it.



I might try an arrangement like



#ifdef __BORLANDC__

#define HugeChar   char huge

#else

#define HugeChar char

#endif



and use HugeChar for the pointers in io.c that I want to be huge.



Cheers



--- PPoint 1.88