dalehenrich/filetree — Issue #13: validation
Author: dalehenrich
Created: 2012-03-05 20:02:59+00:00
State: open

There are two (three including issue #12) places in the package structure where there is potential duplication:

* method chunk
* class chunk

## Method chunk

The method chunk specifies a class and method protocol (category). If the enclosing class directory is renamed or the class in the chunk is renamed, then there is an inconsistency that we can identify at the time that the definitions are created in the image.

If the method protocol starts with a * and does not match the current class (and the method is in a class directory), then we have another inconsistency

If the method protocol starts with a * and does not match the name of the current package (and the method is in the extensions directory) then we have an inconsistency

## Class chunk

If the name of the class specified does not match the enclosing .class directory name that is an inconsistency

If the name of the category for the class does not match the enclosing package name that is an inconsistency..

If we throw an error when the inconsisties are identified during MC defintion creation , we can avoid much confusion later on.