Search found 298 matches

by Martin Meyer
19 Sep 2021 18:19
Forum: Visual Prolog
Topic: Bounded polymorphism problem
Replies: 3
Views: 148

Re: Bounded polymorphism problem

The code below crashes in 64bit mode. The somewhat longer example is an excerpt from a radix set class for keys which support type positive . I suppose the problem stems from same origin as in the before 32bit example: open math, core domains dictionary{Key} = empty; leaf(Key Key); branch(unsigned P...
by Martin Meyer
15 Sep 2021 22:59
Forum: Visual Prolog
Topic: Bounded polymorphism problem
Replies: 3
Views: 148

Bounded polymorphism problem

Hello Thomas, please check this code in 32bit mode (in build 1002): domains dictionary{Key} = leaf(Key). class predicates doNothing : (dictionary{Key} Dict) -> dictionary{Key} NewDict where Key supports unsigned64. clauses doNothing(leaf(K)) = doNothing_1(K). class predicates doNothing_1 : (Key) -> ...
by Martin Meyer
30 Jun 2021 15:19
Forum: Visual Prolog
Topic: Presenters, Symbols, Grammars (WAS: Variables Pending in Debugger Window)
Replies: 3
Views: 462

Re: Presenters, Symbols, Grammars (WAS: Variables Pending in Debugger Window)

My presenter doesn't have side effects. Inside my presenter the fact presentingInstance_terminals is queried, but not asserted. The translation of a terminal number into its text is very fast and cannot cause an overly long presentation. If a program contains more than one (of my) parsers, it is not...
by Martin Meyer
29 Jun 2021 18:19
Forum: Visual Prolog
Topic: Presenters, Symbols, Grammars (WAS: Variables Pending in Debugger Window)
Replies: 3
Views: 462

Presenters, Symbols, Grammars (WAS: Variables Pending in Debugger Window)

(WAS: Variables Pending in Debugger Window ). When you told that the issue has to do with presenters, I remembered that I am using them in a slightly unusual way. I suppose my construction provokes the pending variables display. I want to note however that in build 906 it had worked out well. Let me...
by Martin Meyer
29 Jun 2021 11:52
Forum: Visual Prolog
Topic: Variables Pending in Debugger Window
Replies: 7
Views: 700

Re: Variables Pending in Debugger Window

It seems pending variables do not appear that randomly as I told before. At certain places in my code the effect arises very likely, but at others never.
by Martin Meyer
29 Jun 2021 11:42
Forum: Visual Prolog
Topic: Variables Pending in Debugger Window
Replies: 7
Views: 700

Re: Variables Pending in Debugger Window

When I have sent the bug report, the Variables in the Current Clause was:

Variables in the Current Clause 2.jpg
Variables in the Current Clause 2.jpg (54.63 KiB) Viewed 669 times
by Martin Meyer
29 Jun 2021 11:33
Forum: Visual Prolog
Topic: Variables Pending in Debugger Window
Replies: 7
Views: 700

Re: Variables Pending in Debugger Window

I have sent a bug report from the IDE with comment "Pending variables".
by Martin Meyer
29 Jun 2021 9:30
Forum: Visual Prolog
Topic: Variables Pending in Debugger Window
Replies: 7
Views: 700

Re: Variables Pending in Debugger Window

No, it does not use multiple threads. At least not in 'my' code. I am not sure whether there is some pfc predicate, which I am calling in my program, that internally makes use of multiple threading.
by Martin Meyer
27 Jun 2021 11:38
Forum: Visual Prolog
Topic: Bit Operations
Replies: 1
Views: 453

Bit Operations

Hello Thomas, please check below bit operations example (in build 1001): open bit class predicates getHighBitMask32_oldStyle : (unsigned X) -> unsigned Mask. clauses getHighBitMask32_oldStyle(X) = bitAnd(X_6, bitNot(bitRight(X_6, 1))) :- X_1 = bitOr(X, bitRight(X, 1)), X_2 = bitOr(X_1, bitRight(X_1,...
by Martin Meyer
27 Jun 2021 10:16
Forum: Visual Prolog
Topic: Variables Pending in Debugger Window
Replies: 7
Views: 700

Variables Pending in Debugger Window

Hello Thomas, when I am running the debugger I often see lines of the form "<Variable> pending..." in the Variables in the Current Clause window: Variables in the Current Clause.jpg It seems it happens randomly. But, once it has happened, it tends to be sticky. I.e. when I am going on step...
by Martin Meyer
23 Jun 2021 15:06
Forum: Visual Prolog
Topic: Shift Operator in Build 1001
Replies: 1
Views: 419

Shift Operator in Build 1001

Hello Thomas, thank you very much for providing service build 1001! Updating my code to it I found that the shift operator behaves differently now. I suppose it is not intended: clauses run() :- N = 4 * 8, hasDomain(unsigned64, U64), U64 = 1 << N, stdIo::write(U64). In the new build it outputs 0, bu...
by Martin Meyer
12 May 2021 23:16
Forum: Visual Prolog
Topic: Console main::run() ERROR
Replies: 1
Views: 651

Re: Console main::run() ERROR

Because: Right click in your source text on the predicate name all and select Go to / Go to Declaration . That takes you to the declaration of the list::all/2 predicate: predicates all : (Elem* List, predicate_dt{Elem} Test) determ. The predicate is declared to have predicate mode determ . That mean...
by Martin Meyer
22 Apr 2021 11:31
Forum: Visual Prolog
Topic: Domain range checking for bitwise operators
Replies: 2
Views: 730

Re: Domain range checking for bitwise operators

I think the answer is (Thomas may correct me): The Language Reference says that the operators for bitwise operations are declared (only) on unsigned , unsigned64 , and unsignedNative arguments. When an unsigned8 argument is supplied to the NOT operator it will be converted to the 'best-fitting' doma...
by Martin Meyer
21 Apr 2021 16:16
Forum: Visual Prolog
Topic: Updating to VIP 10
Replies: 3
Views: 923

Re: Updating to VIP 10

Maybe the access violation in 32-bit mode of VIP 10 in this construction goes back to same cause: implement main open core class predicates doNothing : (Type) where Type supports unsigned16. clauses doNothing(X) :- doNothing_1(X, X). class predicates doNothing_1 : (Type A, unsigned16 B) where Type s...
by Martin Meyer
20 Apr 2021 23:48
Forum: Visual Prolog
Topic: Updating to VIP 10
Replies: 3
Views: 923

Updating to VIP 10

Hello Thomas, on updating my code to new VIP 10 the compiler has complained at some surprising places. When I inspected these places in detail, I found that there were bugs in my code which the 9.0.6 compiler (and me) had not noticed before. Apparently the polymorphic type checking has become smarte...