Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!pewter!tenbarge
From: tenbarge@pewter.ucs.indiana.edu
Newsgroups: comp.databases
Subject: Re: Clipper
Message-ID: <20900016@pewter>
Date: 13 Feb 90 03:34:00 GMT
References: <22844@usc.edu>
Organization: Indiana University CSCI, Bloomington
Lines: 23
Nf-ID: #R:usc.edu:-2284400:pewter:20900016:000:1031
Nf-From: pewter.ucs.indiana.edu!tenbarge    Feb 12 22:34:00 1990


/* Written  6:18 pm  Feb 12, 1990 by ajauch@ics.uci.edu in pewter:comp.databases */
In article <22844@usc.edu> atieu@skat.usc.edu (Anthony Tieu) writes:
>Need a review on Clipper, the dBASE compiler. Does it really
>compile dBASE code into EXE files without modifications? How
                                    ^^^^^^ ^^^^^^^^^^^^^
>is it in support, documentation, bugs, etc.? Any experiences,
>good or bad?

From my (albeit limited) experience there are a number of procedures
that differ from dbase 3 to Clipper.  Usually it takes me about three
hours with a Clipper manual to translate a medium size program.  This is
because of Clipper limitations, the modified program still runs under 
dbase fine.
                    ^^^^^^^^^^^
I wouldn't say that the modifications were due to Clipper's limitations but
rather differences in a program that is compiled versus one that is
interpreted.  Also, Clipper enhancements that add to the dBase language are not
part of dBase 3+.


Kris Tenbarge
tenbarge@silver.ucs.indiana.edu