🚀 go-pugleaf

In article <1990Aug10.144500.8901@canterbury.ac.nz>, fore057@canterbury.ac.nz writes:
> In article <9705@rice-chex.ai.mit.edu>, cracraft@wheaties.ai.mit.edu (Stuart Cracraft) writes:
>> Is Turbo Prolog good? What does it do well?
>> Any pro or con ideas? Send to me. I'll summarize.
>> 
>> Stuart
> 
> I do most of my programing in Turbo Prolog.  It has a brilliant development
> environment, with very effective checking of possible error sources, such as
>
...etc.

Ditto for me, in the main.  You should also know that Borland has 
released/given/sold (whatever?) the rights to Turbo Prolog back to the 
original developers who are now marketing it under the name PDC Prolog 
3.2.  PDC is not too different from TP 2.0.  They have added an OS/2 
version (which allows for development of truly enormous programmes), better 
string handling, and networking database predicates like file-sharing 
and file-locking.  Links to Microsoft C 5.1 and TC 2.0 are explicit 
and now C can be the main programme instead of only Prolog as it is in 
TP 2.0  The toolbox has been greatly upgraded including 
predicates for GUI interfaces, mouse support as well as the 
traditional text-based systems offered in the TP version. [Additional 
note: Borland has seen fit to allow PDC to continue using the BGI and 
it is completely supported in the DOS version.]

The language is very strong at building, maintaining and accessing 
databases and other files and in developing user friendly interfaces 
to these sources.  It is *very* efficient of programmer time without 
sacrificing too much in the way of computer efficiency.  What it can't 
do well is produce self-modifying code...a point that has led to flame 
wars as to whether it is *really* Prolog or not.  Short answer is: it 
isn't.  But that is no reason not to buy it if you want to develop 
applications not involving such advanced concepts in (true) Prolog.


DISCLAIMERS:  I love Turbo (PDC) Prolog (and APL) which obviously makes 
me biased in favor of languages that make some sacrifices to computer 
efficiency in the name of my efficiency.  The nice thing about Turbo 
(PDC) Prolog is that--unlike some APLs I've used--the sacrifices in 
computer efficiency are really quite minimal.  [Now if we can just get 
matrix concepts integrated into compiled Prolog...we'll really have a 
language!]  Finally, I have no commercial connection, satisfied 
customer...etc.


John Garland

Bitnet:   jgarland@mun
Internet: jgarland@kean.ucs.mun.ca