Xref: utzoo comp.databases:2748 comp.sys.ibm.pc:30070
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!att!cbnewsc!santol
From: santol@cbnewsc.ATT.COM (shawn.r.antol)
Newsgroups: comp.databases,comp.sys.ibm.pc
Subject: Re: Possible Clipper Bug?
Message-ID: <1225@cbnewsc.ATT.COM>
Date: 12 Jun 89 15:38:21 GMT
References: <506@dcscg1.UUCP>
Distribution: usa
Organization: AT&T Bell Laboratories
Lines: 25

From article <506@dcscg1.UUCP>, by drezac@dcscg1.UUCP (Duane L. Rezac):
> a processing loop that was coded as :   "do while .not. eof() " In DBASEIII, 
> the program ran fine. In clipper, it bypassed the loop. Upon examination with
> debug, I discovered that after Clipper finished indexing the file, it left 
> the database at eof, with eof()=.T. (of course, this caused the do while
> .not.  eof() to fail ;-( ) a "goto top" inserted after the index command
> corrected the problem...

I have experienced this "feature"...  there are other little quirks like this 
too.

P.S.  
Have you used the DOS LINK(er) instead of the PLINK86 linker?
Here is the batch file I use to compile and link using the DOS linker, it is 
much faster!

CL.BAT

clipper %1
if not errorlevel 1 link %1, %1.exe,,\dbase\clipper.lib \dbase\extend.lib

The only dis-advantage is that the DOS linker does not support overlays...
Big deal!

Shawn Antol