Hi, I just finished my work on a R-client for the BaseX XML-database (see CRAN - Package RBaseX ) and am now planning to start working on a similar client in SWI-prolog. The (all) clients are based on raw non-blocking sockets. All input from the client is converted to a raw stream, the server first…

[image] BenEngbers: I can read C and C++ but luckily I have always been able to avoid real programmming in one of those languages :wink:. I am in the same boat. My advise would be to get the code working correctly with Prolog, then when it works as you seek and if speed or some other checkin…

Hi Jan, A C++ interface by a C++ programmer by Volker Wysk post@volker-wysk.de links to a library which dates back to 2004. Is this really the most recent information for interfacing SWI-Prolog and C++?

[image] BenEngbers: A C++ interface by a C++ programmer by Volker Wysk post@volker-wysk.de links to a library which dates back to 2004 GCC 2.95 brings back memories … not all of them good. :wink: This seems to be newer: https://www.swi-prolog.org/pldoc/doc_for?object=section('packages/pl2cp…

Actually, the packaged SWI-cpp.h is the original interface by me. I’m a lousy C++ programmer though. Volker wrote something that is closer to how C++ programmers might want to see Prolog. I have little opinion on that :slight_smile: But yes, the packaged one is maintained and since recently …

It’s been 10+ years since I’ve programmed in C++, so I took a quick look at Google C++ Style Guide to remind myself of the many problem areas in that language. There have been a lot of changes in C++ over the years; for example with copyable and movable types, smart pointers, etc. So, it would be go…

I’m starting to review SWI-cpp.h, by applying the Google style guide. So far, it’s found a number of subtle bugs, mainly to do with implicit casts that weren’t doing what was expected (e.g., treating a size_t as a term_t). I’ve also found some bugs in rocksdb4.pl.cpp that are related, and it wouldn’…

I’m thinking that the use of operator= for unification of terms is a bad idea. Part of the problem is that there’s a default operator= and this can lead to subtle bugs (I’ve already found a few places where implicit conversions caused a bug)… Instead, I propose changing the = operator from, e.g. i…

Hi Peter Sorry I cannot test right now, cause I’m busy with some other work, but in the weekend I could try your changes.

At a conceptual level the only sensible implementation of = between two terms is unification. We notably do not want to copy the term reference itself on =. I’m all in favor of getting rid of ambiguities. We should also be careful that this may be in use in quite a few places and thus break a l…

[image] peter.ludemann: BTW, I think we should move to C++17 … @jan – where would I make the change? Only in the documentation, I guess. The overall policy of SWI-Prolog is to keep its interfaces running on all supported OSes, libraries and tool chains from the oldest to the latest. The l…

Raw to byte or character conversion

Help!

peter.ludemann July 11, 2022, 8:36pm 21

I’ve started a new discussion here: https://swi-prolog.discourse.group/t/changes-to-swi-cpp-h

Topic		Replies	Views
Changes to SWI-cpp.h Discussion discussion	62	3007	July 12, 2023
Install/use swi-prolog for C++ General	16	870	August 19, 2023
Ann: SWI-Prolog 8.5.18 Releases	9	795	October 14, 2022
Ann: SWI-Prolog 9.1.17 Releases	19	581	October 24, 2023
Ann: SWI-Prolog 9.1.0 Releases	7	662	December 7, 2022

Raw to byte or character conversion

Related topics