jezzica85 wrote:So, a BookObject is a book that may contain a List or a Map? Am I understanding correctly? If so, then I don't think this is a good hierarchy. I wouldn't expect to be able to perform the same kinds of operations on a List container as on a Map container, and I'm a little confused what this BookObect is really supposed to represent.
thanks jverd for the suggestion on the naming, but the class isn't actually a book, it's one of many types of object that a book can contain.
jezzica85 wrote:Regardless, "BookObject" doesn't really tell you anything, except that it has something to do with books, and the name "Book" would tell you just as much.
No, BookObject is just sort of a general wrapper class. It has subclasses like BookCharacter, BookSetting, and BookAction, for different parts of the book.