On Wed, Jul 26, 2000 at 03:23:20PM -0700, Peter Scott wrote:
> At 06:18 PM 7/26/00 -0400, you wrote:
> > =pod
> >
> > Here is a nice example of how to add one and one in Perl.
> >
> > =for example
> >
> > print 2 + 2;
>
> I sense a specification mismatch which would not be caught by your proposal :-)
Doh! Okay. I'm just an idiot. And I'm Perl QA! We're doomed.
> Have you seen Damian's design by contract stuff? Your other proposal for
> builtin tests made me think of it. Not a perfect impedance match perhaps,
> but worth considering.
Yes, I attended his Class::Contract talk at TPC. The ideas are
similar in that both take the documentation/English and write it out
in explicit code to be tested. Both have the same problem that
there's no way to check that the contract matches the english
documentation.
Now, while it might be possible to generate API-style docs from the
code contract, I don't think we can do that in general for the docs as
a whole. Although the idea is intriging.
Run some feasibilty tests. See what happens.
--
Michael G Schwern http://www.pobox.com/~schwern/ [EMAIL PROTECTED]
Just Another Stupid Consultant Perl6 Kwalitee Ashuranse
<GuRuThuG> make a channel called Perl, and infest it with joking and
fun....it doesnt make alot of sense.
