I think Ruff, Jeff wrote:
> > ==> Activation: MAIN::padstack-name : f-50 > FIRE 3 MAIN::padstack-name f-50 > Creating Padstack Name > Derived padstack name tpm1620d1 > ==> f-51 (MAIN::capture-padstack) > ==> Activation: MAIN::add-pad-to-jdb : f-51 > Done Opening Jess Engine to calculate pad geometries > "tpm1620d1" tpm1620d1 > Requested View name is com.chipdata.jdb.JDBView@2f1b1a > Found View dip_test > Requested View name is com.chipdata.jdb.JDBView@2f1b1a > Found View dip_test OK, maybe we're getting somewhere now. So if you look above, you see the rule padstack-name being activated, then fired, and then the fact capture-padstack being asserted, which activates add-pad-to-jdb. This means that the rule is on the agenda -- i.e., it's in line to fire when the current rule is finished firing. Now, right after this activation, there's some output which comes from some other code, not the Jess code you showed me. So, my question is: what prints that? One possibility is that the function JDBViewFact prints it (based on the nature of the output and this function's name, that seems possible.) My hypothesis, then, is that the rule padstack-name isn't through firing by the end of the output you've shown me -- i.e, it's calling some other function that doesn't return, so add-pad-to-jdb never gets a chance to fire. --------------------------------------------------------- Ernest Friedman-Hill Distributed Systems Research Phone: (925) 294-2154 Sandia National Labs FAX: (925) 294-2234 Org. 8920, MS 9012 [EMAIL PROTECTED] PO Box 969 http://herzberg.ca.sandia.gov Livermore, CA 94550 -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] --------------------------------------------------------------------
