Timothy S. Nelson wrote: > Also, is there a simple way to know when I should be using a class > vs. a role?
If you plan on creating objects with it, use a class. If you plan on creating classes with it, use a role. -- Jonathan "Dataweaver" Lang
Timothy S. Nelson wrote: > Also, is there a simple way to know when I should be using a class > vs. a role?
If you plan on creating objects with it, use a class. If you plan on creating classes with it, use a role. -- Jonathan "Dataweaver" Lang