A bad Problem message results from an assembly creating instances of a non-built-in top-level kind when the assembly sets a property implying that the instances are objects. In the example below, Inform seems to think that object is a kind of candle for some reason, so that candles being objects produces a circularity; however the real problem is that candles aren't physical objects (if you remove the "lit", then Inform produces a Problem message diagnosing the issue correctly). Also of course there is the "", which presumably arises since this Problem message is also used when a kind circularity is produced by two explicit "X is a kind of Y" assertions.
Steps to reproduce :
Foo is a room.
A candle is a kind.
A lit candle is in every room.
Additional information :
The Problem message:
Problem. You wrote 'A lit candle is in every room' , but that seems to contradict , as it would make a circularity with a candle and an object each being kinds of the other.
Reported by : dfremont
Description :
A bad Problem message results from an assembly creating instances of a non-built-in top-level kind when the assembly sets a property implying that the instances are objects. In the example below, Inform seems to think that object is a kind of candle for some reason, so that candles being objects produces a circularity; however the real problem is that candles aren't physical objects (if you remove the "lit", then Inform produces a Problem message diagnosing the issue correctly). Also of course there is the "", which presumably arises since this Problem message is also used when a kind circularity is produced by two explicit "X is a kind of Y" assertions.
Steps to reproduce :
Additional information :
The Problem message:
Problem. You wrote 'A lit candle is in every room' , but that seems to contradict, as it would make a circularity with a candle and an object each being kinds of the other.
imported from: [Mantis 1587] Nonsense error message on certain assemblies of abstract kinds