Re: SWI-Prolog : Out Of Local Stack
- From: "roschler" <robert.oschler@xxxxxxxxx>
- Date: 20 Sep 2006 07:18:15 -0700
Jan Wielemaker wrote:
On 2006-09-17, roschler <robert.oschler@xxxxxxxxx> wrote:
call(PredCall) is certainly not better than simply PredCall. Looks like
a bug in the debugger. Please report, preferably to the SWI-Prolog
bugzilla system. Include a *complete* program, not just a snippet. Also
include the version, as there have been some recent changes to the
debugger.
--- Jan
Jan,
I have entered a bug report with a complete test program into
SWI-Prolog BugZilla; just follow the reported steps.
In the meantime, is the main liability in using call/1 simply speed,
since it's an interpretive call and not compiled?
Also, is there a way to tell from Prolog code if the code is currently
being traced in the GUI debugger? If there is, and it's not too
ridiculous, I could create a call like:
safe_call(Goal) :-
is_gui_tracing_active,
!,
call(Goal).
safe_call(Goal) :-
\+ is_gui_tracing_active,
!,
Goal.
Too silly?
Thanks,
Robert
.
- Follow-Ups:
- Re: SWI-Prolog : Out Of Local Stack
- From: Jan Wielemaker
- Re: SWI-Prolog : Out Of Local Stack
- References:
- SWI-Prolog : Out Of Local Stack
- From: roschler
- Re: SWI-Prolog : Out Of Local Stack
- From: Jan Wielemaker
- SWI-Prolog : Out Of Local Stack
- Prev by Date: Re: "A Tractable Prolog Implementation"
- Next by Date: List of terms
- Previous by thread: Re: SWI-Prolog : Out Of Local Stack
- Next by thread: Re: SWI-Prolog : Out Of Local Stack
- Index(es):
Relevant Pages
|
