On 1/15/10 8:46 AM, Mark Evenson wrote:
On 1/14/10 3:33 PM, Alan Ruttenberg wrote:
The Jena toolkit has antisocially defined the toString method of an important object to be computationally expensive - it triggers a description logical classification process in some cases, something which can blow out memory or take a very very long time.
[…]
Ouch! I had hoped that the the toString() "contract" in Java entailed a non-computationally expensive result, and that this was widely adopted.
Then a HEADS UP is in order: I committed (~20100112) to SLIME HEAD a patch that invokes the "toString()" method on all JAVA-OBJECTs as a convenience.
[…]
I have (finally) committed the necessary changes to SLIME HEAD (20100128) to make the inspection of toString() results a user interactive action.