On Tuesday, March 25, 2014 6:51:04 PM UTC-7, F.S. wrote: > > Didn't know that you are (were?) a closet Prolog user. ... >
Doh. When I read that: *Now, this should sound familiar if you've ever used Prolog—you're essentially computing the proof tree like a human Prolog interpreter. There is a reason Prolog is called "logic programming"! This is also important as the first way I was introduced to the H-M inference algorithm was by implementing it in Prolog. This is actually surprisingly simple and makes what's going on clear. You should certainly try it. * I forgot that you were quoting the original SO poster. Anyway I still think the core of Leo is a gem that shouldn't be buried inside just Python. If there were a libleo that handles parsing of leo files, serialization, and core outline manipulation API then it could get integrated with editors for other languages where Python is not the first class citizen. A back end leo-qt API would be a bonus. On Monday, March 24, 2014 9:37:05 AM UTC-7, Edward K. Ream wrote: >> >> As some of you know, I recently restarted work on type-related >> programming tools: >> >> https://groups.google.com/forum/#!topic/python-static-type-checking/Vhy_w5bCH8I >> >> The purpose of this project has always been to create new tools **for >> Leo**, so this is (broadly speaking) still part of the Leo project. >> > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
