Re: RFC - Class::Agreement

2005-05-27 Thread Adrian Howard
On 27 May 2005, at 18:25, Ovid wrote: --- Ian Langworth <[EMAIL PROTECTED]> wrote: Reflecting upon this, I'm not even sure why I'd want argument modification as a feature. (Maybe I still had Hook::LexWrap on the brain.) I might just take this out. I vote for taking it out. I view contract

Re: RFC - Class::Agreement

2005-05-27 Thread Adrian Howard
On 27 May 2005, at 16:21, Ian Langworth wrote: [snip] When you say "automatic," I think of source filtering. Do you simply mean an alias for the first argument? If so, I think it's best to leave that up to the programmer. You can always use shift. Fair enough. I just hate having the duplicatio

Re: RFC - Class::Agreement

2005-05-27 Thread Ian Langworth
On 5/27/05, Ovid <[EMAIL PROTECTED]> wrote: > > Class::Agreement's contracts should be > > nearly as light as putting "die unless" in your methods. > > What? I had no idea. Was that in the docs and I overlooked it? To > me, this is probably one of the strongest features of Class::Agreement > a

Re: RFC - Class::Agreement

2005-05-27 Thread Ovid
--- Ian Langworth <[EMAIL PROTECTED]> wrote: > Reflecting upon this, I'm not even sure why I'd want argument > modification as a feature. (Maybe I still had Hook::LexWrap on the > brain.) I might just take this out. I vote for taking it out. I view contracts to be similar to exceptions in one res

Re: RFC - Class::Agreement

2005-05-27 Thread Ian Langworth
On 5/26/05, Adrian Howard <[EMAIL PROTECTED]> wrote: > -No class invariants? Soon! > -You do mention that tweaking @_ in the pre/post blocks will > affect the @_ passed to the method. You don't say that having pre/ > posts that have side effects is evil. You probably should :-) Reflecti

Re: RFC - Class::Agreement

2005-05-26 Thread Adrian Howard
On 23 May 2005, at 15:33, Ian Langworth 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://re

Re: RFC - Class::Agreement

2005-05-23 Thread Ian Langworth
On 5/23/05, Ovid <[EMAIL PROTECTED]> wrote: > 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. Postcondit

Re: RFC - Class::Agreement

2005-05-23 Thread Ovid
--- 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: ht

RFC - Class::Agreement

2005-05-23 Thread Ian Langworth
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 P