Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!shelby!agate!ucbvax!TAURUS.BITNET!raan
From: raan@TAURUS.BITNET
Newsgroups: comp.lang.prolog
Subject: SICSTUS warning question
Message-ID: <2397@taurus.BITNET>
Date: 24 Feb 91 12:10:54 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: yaelsh%csb.cs.technion.ac.il@CUNYVM.CUNY.EDU (Yael Shemesh)
Organization: Tel-Aviv, Israel
Lines: 15

In some prologs, there is a warning and trap to debugger,
when the program encounters an undefined procedure.  This
is the case in SICSTUS.

Does anybody know how, if at all, this behavior can be shut off
in SICSTUS Prolog?

The reason for this question, if you are curious, is that a friend
of mine is writing a program in propositional prolog, and it
is not knowe in "advance" what procedures will be defined, so
it is not possible to define proc :- fail for each of them.

Thanks

-- Ran