I started using Prolog in my self written home automation system over 20 years ago. At first I was using CORBA and I linked ACE/Tao into SWI-Prolog so that Prolog could catch and send CORBA messages. That worked for years but was too annoying to add new message types since a wrapper had to be written for each, plus threading had to be coordinated between C++ and Prolog. Eventually I ditched the CORBA stuff and switched to MQTT, but instead of binding the C++ and Prolog together I found and extended MQTT support for Prolog directly, actually I've mostly replaced the C++ parts of my HA system with Java. The Prolog is pretty nice the way I can now specify predicates for MQTT topic paths, and I use shared topics for scalability. Now all of this is running deployed in k3s.
Extending C with Prolog (1994)
11–20 of 29 posts
Re: Extending C with Prolog (1994)
#12[flagged]
Re: Extending C with Prolog (1994)
#13[flagged]
You (we) may be able to extend that 30 years, one year for each calendar year. Because I'm told LLMs don't really do chained reasoning.
Disclaimer: I'm no expert on LLMs.
Re: Extending C with Prolog (1994)
#14FWIW (not much), around the time of that article, I reversed this: I used Arity Prolog for a morphological parsing program, with C calls for the bit fiddling (because I needed 64 bits, and the Prolog I was using only handled 16 bit strings).
Re: Extending C with Prolog (1994)
#15I started using Prolog in my self written home automation system over 20 years ago. At first I was using CORBA and I linked ACE/Tao into SWI-Prolog so that Prolog could catch and send CORBA messages. That worked for years but was too annoying to add new message types since a wrapper had to be written for each, plus threading had to be coordinated between C++ and Prolog. Eventually I ditched the CORBA stuff and switch…
This sounds really cool and I am glad that Prolog has outlived CORBA
Re: Extending C with Prolog (1994)
#16Earlier quoted context omitted.
Refreshing stories between all the AI ones (and crypto/web3 before that)
Ironically, once upon a time Prolog and logic programming in general were part of the cutting-edge of AI. There's quite a fascinating history of Japan's fifth-generation computing efforts in the 1980s when Japan focused on logic programming and massively parallel computing. My former manager, who is from Japan, earned his PhD in the 1990s in a topic related to constraint logic programming.
I remember when so-called "expert systems" written in Prolog or LISP were supposed to replace doctors. Then came the (first) AI winter after people realized how unrealistic that was.
Nowadays LLMs are supposed to replace doctors.. and that makes even less sense given that LLMs are error-prone by design. They will hallucinate, you cannot fix that because of their probabilistic nature, yet all the money in the world is thrown at people who preach LLMs will eventually be able to do every human job.
The second AI winter cannot come soon enough.
Re: Extending C with Prolog (1994)
#17Is this the time of year when we try to force redditors to stay away by posting about Prolog? I see three stories already.
We need more.
In case you weren't aware, people are using Prolog with LLMs;
Re: Extending C with Prolog (1994)
#18Related: Using Prolog in Windows NT Network Configuration (1996) https://news.ycombinator.com/item?id=36821871
Re: Extending C with Prolog (1994)
#19There's another updated version of that prolog here along with some links, including an archived article from Microsoft Research on how it was (once upon a time) used in Windows NT network configuration:
https://github.com/opless/small-prolog
Re: Extending C with Prolog (1994)
#20[dead]