Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!pacbell.com!ucsd!nosc!humu!pegasus!tleylan
From: tleylan@pegasus.com (Tom Leylan)
Newsgroups: comp.databases
Subject: Re: Clipper 5.01 error message
Keywords: Clipper Arghhhh
Message-ID: <1991May15.212251.23473@pegasus.com>
Date: 15 May 91 21:22:51 GMT
References: <1991May13.223912.1975@gmuvax2.gmu.edu>
Organization: Pegasus,  Honolulu
Lines: 49

In article <1991May13.223912.1975@gmuvax2.gmu.edu> mhovan@gmuvax2.gmu.edu (Mike Hovan) writes:
>
>	Well I have been dueling with Tom in E-Mail, but to show 
>my support for Mr. Deignan I am going to move further comments here.
>Anyway, I started this thread a while back with a question about an
>error message I recieved from clipper 5.01.  I have NOT tracked down
>the problem although I am slowly digging up a little bit of Info
>about the new clipper release.  A release which is STILL buggy, no
>matter what propaganda Mr. Leyland insists on spewing.  
>
>		668:	Eval Stack Fault 
>			Possibly stack underflow ??? (Mr Leyland ?)
>			This error is random, and has not been 
>			reproduced.
>
>	Has anyone figured out how to get a recursive function to run in a
>"SEQUENCE" block?
>
Mike,

You term our conversation "dueling", you continue to mispell my name and
whatever I say is "spewing propaganda".  I also never said that Error 668
was a stack underflow, I used it as a hypothetical example since you insist
that you could fix it if you knew what it was.

My suggestion then as it remains is that you can't fix it if there is an
error in Clipper.Lib and that there is no one-to-one correspondence with
a line of Clipper code and an internal error.  Overflowing the stack can
be fixed by increasing the stack size.  Obviously that grabs more memory
from the free pool, I'm doubtful that the stack is being swapped via VMM
but I don't know for certain.

You seem to be low of memory, that can affect any program, one you wrote or
Lotus 1-2-3 or your favorite accounting program.  Any system that you develop
in Clipper has a smaller RAM footprint than the equivalent system written in
either dBASE IV or FoxPro and approaches that of an equivalent system written
in C.  You will likely doubt that but you need only post your C code that
permits the evaluation of a macro entered from the keyboard to prove me wrong.

Spewing propaganda is in the eye of the beholder and frankly I haven't seen
you answer one Clipper question positively from anyone.  If it is truly
that lousy simply discontinue it's use and the problem is solved.  Besides
spewing propaganda I have developed system in Clipper since it's original
release and have not been happier since the release of 5.01.

There are hundreds of other companies with other compilers who could benefit
from your contructive criticisms.

tom