I have tested the unadwisable project structure. In below the class domain someObj::classDomain is not visible when the code of interface and class is placed in different packages: %%%%%% % This code is in package someInterface interface someObj domains objDomain = unsigned. end interface someObj % ...

Thank you for the info!

I have tried to find an example of a project structure in which the strange behavior would show up. But I have no idea what it could be. Can you give a clue?

Hello Thomas, I am not sure whether it is already known or maybe intended. In an interface the compiler (build 802) does not see domains which are declared in the class having the same name as the interface: interface someObj predicates somePredicate : (someObj::classDomain). %throws Unknown domain/...

OK, fine, and thanks again for explaining everything so well!

Yes, thank you, I understand. My preceding post was insufficient. The solution, which I have in mind, in full, with both object reference and id facts, is like: interface someObj open core properties optRef : optional{someObj}. id : positive (o). end interface someObj %--- class someObj : someObj en...

Would it be cheaper in terms of runtime to create a physical copy of the ID instead of creating an additional object? The semi dead memory will not be reanimated by making a copy. Does memory::getInteger/1-> create a physical copy and is the below code a legal solution? interface myObj open core pro...

Reading it again a question is comming to my mind: Is inserting the object's ID in a list of vacant IDs bringing memory back to live from the finalize predicate? What exactly counts as bringing memory back to live?

Thomas, thank you for the detailed explanation! It is that I am actually using a finalizer in my real code: In my real program there are objects with positive ID numbers. I use these IDs as keys of an array. My program keeps creating and disposing objects as long as it is running. The size of the ar...

Hello Thomas, the garbage collector has a problem to dispose the objects in below code (in VIP build 802). Please have a look. To begin with I take a working code version which creates a number of objects, calls garbageCollect/0 , and in doing so it outputs the number of alive objects. interface som...

Hello Thomas,

I am not sure whether it is intended or you want to change it: The predicate arrayM::add/1-> does not return the index of the added element, but the index plus 1.

I supposed the constant in my example is null terminated, because the Language Reference says When creating a binary constant the compiler adds the EOS symbol immediately after this constant, which makes safe the directive usages like this: constants text : string = uncheckedConvert(string, #binincl...

Maybe the #bininclude compiler directive could help you. By it your text file can be included as a binary. The binary can be converted then to a string. To demonstrate it take for example main.pro as the text file. It is coded in UTF-8 with a leading byte order mark of 3 bytes. Create a new console ...

Hello Thomas, in unionFind.pro is a predicate which does the path compression: predicates find_node2 : (node{@Node} Node) -> node{@Node} Component. clauses find_node2(Node) = Component :- Parent = Node:parent, if Node = Parent then Component = Node else Component = find_node2(Parent), Node:parent :=...

I see. Thanks again for answering!

I have an add-on question. Probably you can answer it too:

Is it legal in a finalizer to store the object (i.e. This) in a class fact and thereby abandon the disposal of the object?