The result you show looks like the thing we have called a msStringSeq (Microsoft String Sequence). There are predicates in the windowsApi class for converting to and from such "sequences": domains msStringSeq = pointer. % @short A sequence of null (two bytes) terminated Unicode strings. % The sequen...

You don't actually ask any question, but I guess you wonder how the code works? Or alternatively that you wonder why you can't follow the expected behavior in the debugger? Conceptual behavior The second parameter of add1 is an output parameter. If I introduce a Result variable in the second clause,...

Thank you, we will look at it.

Yes, there is a problem. We will look at it. For now you can write:
Using hasDomain like that ensures that the operation is performed as a unsigned64 bit operation.

The choices in in the "yale key" depends on what is present in the project. In earlier days the tabControl would be present by default, but now you will have to add it explicitly: locate $(ProDir)\pfc\gui\controls in the project tree Right click the node an select Add.. in the context menu Browse to...

array2M has 0-based indices. But if you ignore the 0 indices and just make the array one larger at each dimension then you can use 1-based indices. The initialization code can look like this: Size = 4000, Array = array2M::new(Size + 1, Size + 1), foreach N = std::fromTo(1, Size) do foreach M = std:...

Visual Prolog 9 build 906: trailingZeroBits64 has been added to bit , and bit counts has been changes to positive predicates bitCount : (unsigned Value) -> positive Count. bitCount64 : (unsigned64 Value) -> positive Count. % @short Returns the number of non-zero bits % @end predicates isPow2 : (unsi...

This problem is solved in Visual Prolog 9 build 906.

(The problem occurred for all editor content sizes N * 8192 - 1).

This problem is solved in Visual Prolog 9 build 906.

This problem has been solved, but unfortunately we forgot to merge it into Vip 9 (903-905).

It is not a problem to add such a predicate. But I wonder whether the result should be an unsigned64 or an unsigned (clearly the number is at most 64, so it will easily fit into an unsigned)?

Sometimes you may see errors that comes from lacking #include directives. The #include directive may have been inserted automatically, but too late the error was already listed. Building again usually solves that kind of problems.

Next time you may rename <project>.env instead and compare the files and/or send it to us.

Thank you, I can reproduce the problem, and will look at it.

Sounds like it could be more convenient. The purpose of the change is to ensure that there is only one Vip 9 uninstaller . The "old" installers worked like "individual" products, but that also means that there is an uninstall entry for each version you have installed. And uninstalling any of them wi...