Page 1 of 1
Referencing non-existing rules should generate an error
Posted: Sun May 10, 2009 7:43 am
Sometimes after changing a rule name I forget updating a call to that call, thus calling a rule which doesn't exist. Currently (2.2) this is simply ignored by CFDG. I'd rather see an error message, though, since this simply is an error and I can't imagine a situation where ignoring it would be a good idea.
Posted: Sun May 10, 2009 8:19 am
When I modify mtree.cfdg to change one of the calls to rule WL to WLb I get the error message
Shape with no rules encountered: WLb.
Is this the situation that you are talking about?
Posted: Sun May 10, 2009 11:09 am
Yes, that's what I was talking about. I just noticed I was still running 2.2beta3 (v9). Using the final release (v10) it works like you describe. Sorry for the confusion.
I thought I was running the final 2.2 version, since beta3's output said "cfdg - 2.2(v9)"...
Posted: Sun May 10, 2009 6:31 pm
I'll be more careful with future beta releases.