Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!spool.mu.edu!uwm.edu!ux1.cso.uiuc.edu!usenet
From: tmkk@uiuc.edu (K. Khan)
Newsgroups: comp.databases
Subject: Re: Clipper 5.01 bugs
Message-ID: <1991May20.220820.22460@ux1.cso.uiuc.edu>
Date: 20 May 91 22:08:20 GMT
Article-I.D.: ux1.1991May20.220820.22460
References: <1991May17.211857.18269@pegasus.com> <1991May14.170431.1509@ux1.cso.uiuc.edu> <1991May15.210031.23270@pegasus.com> <24450@gremlin.nrtc.northrop.com>
Sender: usenet@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 21


In article <1991May17.211857.18269@pegasus.com> tleylan@pegasus.com (Tom Leylan) writes:
>
>Nantucket isn't blind, their development group aren't incapable of writing
>dBASE IV, the prefer not to.  I sat in Larry Heimendinger's office and told
>him to expect to lose the low-end dBASE user who only used Clipper as a
>"packager" to compile their final dBASE III application.  I believe that
>they will gain from the top end however, the programmers who could write the
>app in C or Pascal but for various reasons (usually productivity) they will
>choose to use Clipper now.

I hate to tell you this, but Nantucket might just lose BOTH ends. I
programmed in C many years before I ever wrote one line of Clipper code.
I confess, I liked the C-like features of Clipper 5.0, and I use them
extensively in my applications, but all that means nothing if the
application which results is unstable.

If I had my druthers, I would write everything in C and use the Paradox
engine or some other database function library, perhaps along with some
sort of CASE tool. This may be where the "high-end" programmers will end
up.