Menu
▾
▴
Re: [Yap-users] Catching up to SWI-Prolog
|
From: Douglas M. <log...@gm...> - 2016-02-10 18:22:56
|
I was setting up my February 2016 todo list for SWI-Prolog .... https://github.com/logicmoo/swipl-devel-unstable/issues/ With my Higherlevel goals here https://github.com/logicmoo/swipl-devel-unstable And here was the rub: After I am done I will still be not be as performant as I want AND I will have merely duplicated work done in YAP already. So I am thinking Getting YAP caught up to doing the things SWI-Prolog does will take less time than catching up SWI-Prolog.. Though I started adding tabling to SWI it will be multitudes slower than normal code which by another factor is still slower yet comparatively to YAP Whereas it should not take and longer than 6 months to get YAP caught up and have all of SWI-Prolog feature and packages working.. It might take a couple years to get SWI-Prolog up to the speed of YAP.. (Both these figures are wrong except for the proportions) If Jan is more interested in doing new and exciting things and the tooth to tail time for fixing up the swi-kernel is just too expensive.. He probably needs to stay in boring bug fixing mode with SWI and develop the applications he wants Example: would having JIT-LLVM in SWI-Prolog make SWISH any better? No. Also, If some other developer started hacking on SWI's kernel anding these things JIT-LLVM /Tabling etc .. Is that going to make it easier for Jan to do more interesting things? No, he'll be helping and sorting out the development and goals. (A distraction) https://github.com/logicmoo/yap-6.3/issues > So I am going to spend Feb/March 2016 experimenting with the opposite > approach: > > 5 Open > <https://github.com/logicmoo/yap-6.3/issues?q=is%3Aopen+is%3Aissue> 0 > Closed > <https://github.com/logicmoo/yap-6.3/issues?q=is%3Aissue+is%3Aclosed> > Author > Labels > Milestones > Assignee > Sort > > - <https://github.com/logicmoo/yap-6.3/issues?q=is%3Aissue+is%3Aopen> > XSB verify_attributes/2 attv_unify/2 INFRA to be called between > verify_attributes/3 and attr_unify_hook/2 > <https://github.com/logicmoo/yap-6.3/issues/5> > #5 opened 6 minutes ago by logicmoo > <https://github.com/logicmoo/yap-6.3/issues?q=is%3Aissue+is%3Aopen+author%3Alogicmoo> > > 0 <https://github.com/logicmoo/yap-6.3/issues/5> > - <https://github.com/logicmoo/yap-6.3/issues?q=is%3Aissue+is%3Aopen> > PORT library(pack) works in YAP (do any porting) With the end goal to > even use SWI's hosting site to exchange packs > <https://github.com/logicmoo/yap-6.3/issues/4>enhancement > <https://github.com/logicmoo/yap-6.3/issues?q=is%3Aissue+is%3Aopen+label%3Aenhancement> > #4 opened 16 minutes ago by logicmoo > <https://github.com/logicmoo/yap-6.3/issues?q=is%3Aissue+is%3Aopen+author%3Alogicmoo> > > 0 <https://github.com/logicmoo/yap-6.3/issues/4> > - <https://github.com/logicmoo/yap-6.3/issues?q=is%3Aissue+is%3Aopen> > Ensure library(pengines) works in YAP (do any porting) > <https://github.com/logicmoo/yap-6.3/issues/3> > #3 opened 19 minutes ago by logicmoo > <https://github.com/logicmoo/yap-6.3/issues?q=is%3Aissue+is%3Aopen+author%3Alogicmoo> > > 0 <https://github.com/logicmoo/yap-6.3/issues/3> > - <https://github.com/logicmoo/yap-6.3/issues?q=is%3Aissue+is%3Aopen> > Ensure new library(prolog_streams) or equivalent is in YAP > <https://github.com/logicmoo/yap-6.3/issues/2> > #2 opened 20 minutes ago by logicmoo > <https://github.com/logicmoo/yap-6.3/issues?q=is%3Aissue+is%3Aopen+author%3Alogicmoo> > > 0 <https://github.com/logicmoo/yap-6.3/issues/2> > - <https://github.com/logicmoo/yap-6.3/issues?q=is%3Aissue+is%3Aopen> > Port SWICLI ( my .NET/MONO clone of JPL ) from SWI-Prolog to YAP This > will be a good introduction to YAP FFI > <https://github.com/logicmoo/yap-6.3/issues/1> > #1 opened 21 minutes ago by logicmoo > <https://github.com/logicmoo/yap-6.3/issues?q=is%3Aissue+is%3Aopen+author%3Alogicmoo> > http://www.swi-prolog.org/pack/file_details/swicli/doc/api.html > > > > This includes ClioPatria/SWISH etc > |
