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

2000-07-26 Thread Tom Christiansen
I already did that. I ran it on the Cookbook code. Yes, some things didn't work out for such reasons as you state. That's not the point. The point is that what you suggest is too much work. You aren't ever going to get people to add all your gratuitous lint-happiness inserts to all their docs.

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

2000-07-26 Thread Tom Christiansen
>On Wed, Jul 26, 2000 at 04:22:37PM -0600, Tom Christiansen wrote: >> Too complicated. Don't make people change anything. Simply -cw syntax >> check anything you can, and don't try to incite a revolution or onerous >> burdens worrying about the fringe cases. I

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

2000-09-07 Thread Tom Christiansen
>It does. >no warnings 'uninitialized'; >Given that "uninitialized value" are some of the most common spurious >warnings, (I personally code to check for definedness) it may make >sense for the default to be the equivalent of: >use warnings; >no warnings 'uninitialized'; >Everyone

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

2000-09-07 Thread Tom Christiansen
>What I think might be more interesting 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. Argh, no! --tom

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

2000-09-07 Thread Tom Christiansen
>Despite the groans from the peanut gallery, Whatever. We've got too damned many falsies already. >Funny thing is, I can't think of a case at the moment where such >information would be useful. I'm also a little worried about >implementing the details of such a propsal. Consider the followin

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

2000-07-26 Thread Tom Christiansen
Too complicated. Don't make people change anything. Simply -cw syntax check anything you can, and don't try to incite a revolution or onerous burdens worrying about the fringe cases. It's not important enough. --tom

Pre-RFC: undef =~ s/def/initialize/

2000-09-08 Thread Tom Christiansen
>So you wouldn't be in favour of: >my Dog $spot; >print defined($spot) ? 'defined' : 'undefined'; # undefined >print $spot->isa('Dog') ? 'Dog' : 'not dog';# Dog; >then? >Bang goes that RFC... No, I would argue that undef() be changed to uninitialize(). This is infinitely better

Re: Pre-RFC: undef =~ s/def/initialize/

2000-09-17 Thread Tom Christiansen
>Personally, I still think that >my @foo; # uninitialized >my @bar = ();# initialized, but empty >should be different. That's because you're not thinking of undef as a particular SV. --tom