--- Ian Langworth <[EMAIL PROTECTED]> wrote: > I'm working on a new module, Class::Agreement, and I've started by > writing the documentation. If anyone has a few minutes, I'd like some > feedback as to whether my descriptions of the concepts make sense and > if you like the syntax. > > HTML: http://reliant.langworth.com/~ian/Class-Agreement.html > > POD: http://reliant.langworth.com/~ian/Class-Agreement.pod
Hi Ian, In discussing the benefits, I didn't think you made a strong argument. However, in reading the page your docs points to, I think the argument can be improved with this: Precondition violations mean that the client is in error. Postcondition violations means that the supplier is incorrect. I also noticed you didn't make a comparison to Class::Contract. I think something explicit would be useful. You did write "Class::Agreement is also the only implementation in any language to blame failed contracts correctly", but I don't know what that means. I also note that the link you point us to after that comment is a citation, not something I can actually read. Other than that, it looks interesting. Cheers, Ovid -- If this message is a response to a question on a mailing list, please send follow up questions to the list. Web Programming with Perl -- http://users.easystreet.com/ovid/cgi_course/
