Peter Ludemann

The main bug is: https://bugs.python.org/issue40360 (and also https://bugs.python.org/issue36541). I think that there's a fairly straightforward way of wrapping the new Python parser to give the necessary functionality that "Black" (and...

Does this mean that the various `PL_put_*()` functions are obsolete/deprecated? If a `PL_get()` with CVT_EXCEPTION fails, does this mean that `PL_exception(0)` should always be called? E.g.: ``` if ( !PL_get_wchars(t,...

On Thu, 4 Aug 2022 at 03:00, Jan Wielemaker ***@***.***> wrote: > Does this mean that the various PL_put_*() functions are > obsolete/deprecated? > > The ones dealing with text...

About trail with `PL_unify_*()` ... this only applies for variables that are older than the current choice point (more-or-less), so PL_new_term_ref; `PL_unify_*()` wouldn't create an entry on the trail, would...

I thought that local variables are never trailed; only sufficiently old global variables. But perhaps the meaning of "local variable" is different when inside a foreign function? There's this comment...

The more important question (for me) is knowing which functions in `SWI-Prolog.h` are deprecated. (Because I only want to use non-deprecated functions in `SWI-cpp.h`. Anyway, it seems that (for now,...

I get a similar error. ``` $ uname -a Linux penguin 5.10.110-15808-ge5740beba59b #1 SMP PREEMPT Tue May 24 10:50:29 PDT 2022 x86_64 GNU/Linux $ swipl --version SWI-Prolog version 8.5.12 for...

The example on the github page works fine with swipl 8.4.3. However, 8.4.3 is quite old and most SWI-Prolog users have the development version (8.5.12), which has added quite a...

Perhaps pyswip should check the SWI-Prolog version and throw an exception if it isn't what's expected. https://www.swi-prolog.org/pldoc/doc_for?object=c(%27PL_version_info%27)

Works for me on Ubuntu with 8.5.14 ``` $ swipl Welcome to SWI-Prolog (threaded, 64 bits, version 8.5.14) SWI-Prolog comes with ABSOLUTELY NO WARRANTY. This is free software. Please run...