Dear all, I'm not sure whether to write you or not - out of two reasons: First of all, I've deteced a behaviour of ECLiPSe so strange that I normally would think of as an error on my side. But because I found a similar error before - the one with consecutive constant assignments - I'm not so sure about ECLiPSe anymore. So I though you might be interested. Secondly, I did not isolate the bug/behaviour. It is deeply hidden in my code and it would take some time to peel it out - as it did hours to bould down the consecutive constant assignments bug into a couple of lines, and then you said "Oh, we already know this bug." Maybe you know this too: The following lines of code: writeln(["X0", PDDL_Variable]), The_Type2 = type with [ id: ID, objects: Objects, name: TypeName ],true, printf("xxx", []), writeln(["X1", PDDL_Variable]), is traced like this S (18305) 11 CALL writeln(["X0", V_5643]) %> creep [X0, V] S (18305) 11 EXIT writeln(["X0", V_5643]) %> creep S (18306) 11 CALL printf(type(t_1, [], "t_1", [object, t__3], [], [], [t_1, t_1x, ...]), []) %> creep S (18306) 11 FAIL printf(..., ...) %> It also fails without trace. BTW, the type(...) in the printf is the one bound to The_Type2 I assure you, there is no other printf anywhere near these lines. You know, if you build a large program with a language, things like these give you strange feelings.. Nevertheless, thank you for providing ECLiPSe and giving lots of support. Uli -- Ulrich Scholz scholz@informatik.tu-darmstadt.de http://www.intellektik.informatik.tu-darmstadt.de/~scholzReceived on Thu Jan 30 15:50:43 2003
This archive was generated by hypermail 2.1.8 : Wed 16 Nov 2005 06:08:19 PM GMT GMT