Re: Bug tracking and todo tests

2001-02-26 Thread Chaim Frenkel
w how to discover the -I options that I was KS> called with. Any ideas? I ran into that problem with some code I was developing, and I belive I posted a feature request, that there should be some way of getting the full command line arguments back. -- Chaim Frenkel

Re: Pre-RFC - "use warnings" by default for all non-one-liners

2000-09-07 Thread Chaim Frenkel
teresting or useful would be to have another undef type. Call it uninit. THis would be only used for data that hasn't been initialized. Then there would be two warnings one for unitialized and one for using undef. It might be better done by doing some kind of dataflow, but that is tricky.

Re: Pre-RFC - "use warnings" by default for all non-one-liners

2000-09-07 Thread Chaim Frenkel
ne that I like the most. I'm usually marshalling large quantities of data, and I like to know (or at least be able to backtrack) when some piece of data was missing. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: Pre-RFC - "use warnings" by default for all non-one-liners

2000-09-05 Thread Chaim Frenkel
Perhaps if -w has a level. (Somewhat coarser than lexical. With a family of these 'known' warnings not emitted.) -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: Pre-RFC - "use warnings" by default for all non-one-liners

2000-09-04 Thread Chaim Frenkel
t.) I don't think telling folks to add a no warnings to the code just before release, is the way. PERL5OPT seems a bit of the wrong approach. And the -M-warnings, is taking up a lot of room on the #! line. *sigh* -- Chaim Frenkel

Design by Contract for perl internals

2000-08-13 Thread Chaim Frenkel
alpha and beta testing, the conditionals would be active and verifying the specifications. During ship and user testing, they would be off. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC 79 (v1) Code which is both executable and POD.

2000-08-10 Thread Chaim Frenkel
hand holding. With an active style sheet (i.e. embedded perl code) it may be doable by a generic parser/emitter. But I'm no SGML/XML/ whateverML guru. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC: Automated Testing Of Code Examples In Documentation and "=for example"

2000-07-27 Thread Chaim Frenkel
>>>>> "MGS" == Michael G Schwern <[EMAIL PROTECTED]> writes: MGS> On Wed, Jul 26, 2000 at 09:01:22PM -0400, Chaim Frenkel wrote: >> If you do this for new code or changed documentation adding >> a =for result would add more test cases. MGS> Sor

Re: RFC: A Test For Every Patch

2000-07-27 Thread Chaim Frenkel
; == Michael G Schwern <[EMAIL PROTECTED]> writes: MGS> On Wed, Jul 26, 2000 at 08:51:18PM -0400, Chaim Frenkel wrote: >> I'd like to reject the philosophy. I'd prefer that the language define >> perl. I.e. not an implementation. Rather the spec. >> >> Shou

Responses to RFC.

2000-07-27 Thread Chaim Frenkel
I haven't seen any responses to my responses to the RFC. Is this list working? Or is it my software? P.S. Why is this perl-qa? Shouldn't it be perl6-qa? -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL

Re: RFC: Automated Testing Of Code Examples In Documentation and "=for example"

2000-07-26 Thread Chaim Frenkel
GS> =pod MGS> Here is a nice example of how to add one and one in Perl. MGS> =for example MGS> print 2 + 2; MGS> The existing POD utilities would have to be modified to consider "=for MGS> example" as Perl

Re: RFC: JART - Just Another Regression Test

2000-07-26 Thread Chaim Frenkel
sing almost the entire range of Perl and all with the same output! -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183

Re: RFC: A Test For Every Patch

2000-07-26 Thread Chaim Frenkel
ance. Period. MGS> While this may seem draconian, it should rapidly raise the overall quality MGS> of the patches by forcing authors to do more than dash off a little C code. -- Chaim FrenkelNonlinear Knowledge, Inc. [EMAIL PROTECTED] +1-718-236-0183