On Fri, Dec 3, 2010 at 9:56 AM, Tom Christiansen wrote:
>
>> after I posted my series of patches to perlipc.pod , I saw that
>> tchrist posted his version, which got accepted immediately. As a
>> downside to that, I'll have to restart my work. However, I noticed
>> that perlipc.pod still has many
On 4 December 2010 17:43, Tom Christiansen wrote:
>> I think we would both agree that that is way to much. And I
>> automatically assume code with "use utf8" in it is subtly
>> broken until proved otherwise anyway. :-)
>
> Oh drat! That's distressing. I some time ago reached the conclusion
> tha
>> It's the isolated snippets like the zillion I last night pointed out in
>> perlfunc where I feel all the declaration detracts from the point.
>>
>> If you believe that every possible example in Perl needs to be fully
>> declared, than by all means do so. But make sure you always start every
>>
On 4 December 2010 16:29, Tom Christiansen wrote:
> Yves wrote:
>
>> Well, that is not entirely correct. Some /are/ full blown programs.
>
> *Those* I do try to always my() or our() or state() or sometimes
> even local(), which is indeed appropriate in places:
>
> use Carp qw< :DEFAULT cluck >;
On Sat, Dec 04, 2010 at 04:10:36PM +0100, demerphq wrote:
>
> I don't buy that. Lots and lots and lots of programmers, including
> well known ones, started off by typing example programs into their
> computers.
That's one thing. The other thing is to copy-and-paste some code fragment
from documen
Yves wrote:
> Well, that is not entirely correct. Some /are/ full blown programs.
*Those* I do try to always my() or our() or state() or sometimes
even local(), which is indeed appropriate in places:
use Carp qw< :DEFAULT cluck >;
if (something_or_other) {
local $SIG{__WARN__} =
On 4 December 2010 15:18, Abigail wrote:
> On Fri, Dec 03, 2010 at 05:08:42PM -0800, chromatic wrote:
>> On Friday 03 December 2010 at 16:53, Leon Timmermans wrote:
>>
>> > We do, honestly. I'm tired of having to explain to newbies why the
>> > official perl documentation is not strict friendly, w
>> I don't believe you.
> Are you suggesting I'm lying??
No. I'm saying that I find it unbelievable. Perhaps
you have a selective memory. Perhaps you are forgetting
things, or remembering others.
But yes, I mainly teach programmers programming.
I don't have a great deal of success with nonpr
On Sat, Dec 4, 2010 at 5:13 AM, Tom Christiansen wrote:
> Then they just aren't smart enough to handle programming, I guess.
What would be so stupid about that question? What would you reply if
someone asked you that question?
> I have never ever had the least problem. I've taught many thousand
On Fri, Dec 03, 2010 at 05:08:42PM -0800, chromatic wrote:
> On Friday 03 December 2010 at 16:53, Leon Timmermans wrote:
>
> > We do, honestly. I'm tired of having to explain to newbies why the
> > official perl documentation is not strict friendly, when I tell them
> > they should use strict. **I
There *are* real problems in the documenation.
But the fact that something is described as
sin($x)/cos($x)
without a my declaration, is *not* one of them.
The biggest problem is that it is too hard to find the right
information where you're looking for it, because it's scattered
all over t
I was simply showing which examples from perlfunc
are wrong by the high and mighty approach.
It is ridiculous to insist on mying them all.
That was my point.
--tom
12 matches
Mail list logo
