From: Stefan K. <skr...@gm...> - 2016-07-29 15:57:57
|
Hi Andrew, a meta-interpreter is a good start. Which impure features do you use? Control flow stuff like cut and if-then-else? All-solution predicates like setof/3? Exceptions? Are you in control of the code that the meta-interpreter runs -- or is it contributed by some third party? Best Regards, Stefan. PS. So... how about moving the discussion to SO? On Jul 29, 2016 16:46, "Cropper, Andrew" <a.c...@im...> wrote: > Hi Stefan, > > I have replicated this by writing a meta-interpreter which keeps track of > the number of resolutions, which I will extend to include a resolution > limit. Although this solution works for my problem, it is not general > purpose because the meta-interpreter can only handle pure Prolog. > > Hope that helps a little, > > Andrew > > > > > > > > On 27 Jul 2016, at 21:08, Cropper, Andrew <a.c...@im...> > wrote: > > > > Hi Stefan, > > > > One option would be to replicate the SWI predicate in YAP, but this > seems a big job. I may be wrong but I think that YAP does not record the > number of inferences, so it would require a change there. > > > > We can move the discussion to StackOverflow. > > > > Kind regards, > > > > Andrew > > > > > > > > > > > > > > > >> On 27 Jul 2016, at 11:54, Stefan Kral <skr...@gm...> wrote: > >> > >> Hi Andrew, > >> > >> I'm looking for exactly the same feature too! > >> > >> Unlike you, I require a portable solution, as my primary Prolog > processor is SICStus Prolog—not YAP. That being said, let me emphasize that > I would love to see said feature in YAP, too, of course... what else?! > Right now, I cannot offer a working solution, but I can offer perspective: > >> > >> Let's move this discussion to StackOverflow! It addresses a much larger > audience and encourages cross-fertilization between different Prolog > processors (I hope). > >> > >> What are your thoughts on this? I'm looking to hearing from you soon! > >> > >> All the best, > >> Stefan. > >> > >> > >> On Jul 27, 2016 11:52, "Cropper, Andrew" <a.c...@im...> > wrote: > >> Hi all, > >> > >> I would like to enforce a limit on the number of inferences allowed to > find a solution for a given goal. This idea is akin to the > call_with_inference_limit(:Goal, +Limit, -Result) predicate in SWIPL. > >> > >> I have looked through the YAP documentation and there seems to be no > obvious way to do this. Has anyone tried to do this before, or know of a > relatively simple way to implement this? > >> > >> Thanks, > >> > >> Andrew > >> > ------------------------------------------------------------------------------ > >> What NetFlow Analyzer can do for you? Monitors network bandwidth and > traffic > >> patterns at an interface-level. Reveals which users, apps, and > protocols are > >> consuming the most bandwidth. Provides multi-vendor support for NetFlow, > >> J-Flow, sFlow and other flows. Make informed decisions using capacity > planning > >> reports.http://sdm.link/zohodev2dev > >> _______________________________________________ > >> Yap-users mailing list > >> Yap...@li... > >> https://lists.sourceforge.net/lists/listinfo/yap-users > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Yap-users mailing list > > Yap...@li... > > https://lists.sourceforge.net/lists/listinfo/yap-users > > |