Hello Thomas,

I am bringing this issue back to the top because it (still or again) needs a treatment (in build 902).

Hello Thomas, this works (in build 902): class predicates p : () -> Dom where Dom supports integer. clauses p() = 1 + 0. But with these variants there is some problem: class predicates p1 : () -> Dom where Dom supports integer. clauses p1() = 1. % raises: 1 is not in the domain 'Dom' class predicate...

Hello Thomas,

please check this code (in build 902). It dumps:

Hi hyphz,

are you searching for the pfc help file? If you install Visual Prolog to folder
"C:\Program Files (x86)\Visual Prolog 9 PE\" then the help file will be
"C:\Program Files (x86)\Visual Prolog 9 PE\appData\doc\vip.chm".

I have created a link to the file in my start menu.

Thank you for answering! No else questions in this post. Just my thoughts/remarks in case you want to read them. Anyway, it is a fundamental property of Visual Prolog ... Yes, I see. Changing a fundamental property can turn a lot of things upside down. I can imagine that it could easily produce an u...

OK. In the Language Reference it reads but: constants and domains defined in an interface are not part of the type that the interface denotes But these matters are a question of how to formulate the theory (and you are doing that always concisely very well). What I want to tell by the thread is howe...

Yes. However why must that imply, we cannot refer via objC to the constants/domains of the interfaces it supports, i.e. to const1 and dom1 ? An interface uniformly exhibits predicates/properties originally declared in it as well as those it supports. Why to treat constants/domains differently in thi...

Hello Thomas, VIP's object system is sound and powerful. Its latest add-on "bounded polymorphism" is working already fine in my code. The only issue about the object system which I think is questionable, is the difference interfaces impose on their type and scope. You have explained it in Interface ...

This works too: interface obj0 predicates p : (). end interface obj0 %=== interface obj1 supports obj0 end interface obj1 %=== interface obj2 supports obj1 end interface obj2 %=== interface obj3 predicates from obj2 p/0 end interface obj3 But that does not: interface obj0 predicates p : (). end inte...

Thank you for the info! In some cases it works however to not refer to the original declaration: interface obj0 predicates p : (). end interface obj0 %=== interface obj1 predicates from obj0 p/0 end interface obj1 %=== interface obj2 predicates from obj1 p/0 end interface obj2 I would vote for that ...

Hello Thomas, please have a look at this predicates from - supports - predicates from construction (in build 902): interface obj0 predicates p : (). end interface obj0 %=== interface obj1 predicates from obj0 p/0 end interface obj1 %=== interface obj2 supports obj1 end interface obj2 %=== interface ...

Hello Thomas,

please check again the initial example code in build 901. It looks like the fix has not been taken to version 9.

Thank you! I have applied the fix and it works fine.

It is the goal from the console application template.

Hello Thomas, please have a look at this code. It raises exception couldNotCreate in a class initializer, it outputs however error r000 (in VIP 900): class someClass end class someClass %--- implement someClass class facts flag : boolean := true. class predicates initialize : () [classInitializer]. ...