Re: SWI-Prolog : Out Of Local Stack
- From: Jan Wielemaker <jan@xxxxxxxxxxxxxxxxxxx>
- Date: 20 Sep 2006 18:54:30 GMT
On 2006-09-20, roschler <robert.oschler@xxxxxxxxx> wrote:
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.
Fixed. See updated bug report (and mail if all went as it should).
In the meantime, is the main liability in using call/1 simply speed,
since it's an interpretive call and not compiled?
call(X) and X are the same. The current version simply defines
call(X) :- X.
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?
Bugs should be fixed at the right place. You can check whether the
tracer is active using tracing/0 and the gui tracer using
current_prolog_flag(gui_tracer, true). Very exceptional cases
aside, never use this in your application.
Thanks for reporting --- Jan
.
- References:
- SWI-Prolog : Out Of Local Stack
- From: roschler
- Re: SWI-Prolog : Out Of Local Stack
- From: Jan Wielemaker
- Re: SWI-Prolog : Out Of Local Stack
- From: roschler
- SWI-Prolog : Out Of Local Stack
- Prev by Date: List of terms
- Next by Date: Re: Prolog programming job?
- Previous by thread: Re: SWI-Prolog : Out Of Local Stack
- Next by thread: socket programming
- Index(es):
Relevant Pages
|
