From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,FREEMAIL_FROM, INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,24ac4e1c8cbfe3c X-Google-Attributes: gid103376,public From: "Vladimir Olensky" Subject: Re: histrionics Date: 1999/09/11 Message-ID: #1/1 X-Deja-AN: 523713015 References: <37D670CE.855F96BD@interact.net.au> <37D678E4.9867000B@interact.net.au> <37d74de9@eeyore.callnetuk.com> <7r8c60$b2q$1@nnrp1.deja.com> <7r9rkj$g75$1@nnrp1.deja.com> <7rcckp$b12$1@nnrp1.deja.com> Organization: Posted via Supernews, http://www.supernews.com X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Newsgroups: comp.lang.ada X-Complaints-To: newsabuse@supernews.com Date: 1999-09-11T00:00:00+00:00 List-Id: Robert Dewar wrote in message <7rcckp$b12$1@nnrp1.deja.com>... >In article , > "Vladimir Olensky" wrote: >> Another thing is that it may be difficult for many people to >grasp >> the idea of backtracking and recursion and be able to >understand >> program execution that uses them. > >No, in Prolog, the difficulty is not understanding the >backtracking, that's the easy part, or it would be easy >if it were pure, but the cut operator is like falling >off a semantic cliff, and the frequent need to use cut >is a severe disappointment. I had this in mind when was talking about backtracking. In Prolog cut operator significantly complicates comprehending of the backtracking process. Regards.