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
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
Vsevolod (Simon) Ilyushchenko wrote:
> Hi,
>
> I'd like to suggest a module that I came up with to test CGI file
> uploading logic. I have not found anything else like it.
have you seen Apache-Test yet?
http://search.cpan.org/dist/Apache-Test/
I find it hard to understand modules like this a
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
--- 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
Jim,
"test" in what sense? Is this supposed to be a module like Test::More
or Test::Deep which builds on Test::Builder and which will ultimately
generate an 'ok'? If so, what does the interface for that look like?
It'll look like this: (in a Test::Unit::TestCase subclass)
my $fh =C
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
