Re: Regular Expression Quick Reference

2003-07-27 Thread Tom Christiansen
+ lc Lowercase a string + lcfirst Lowercase first char of a string + uc Uppercase a string + ucfirst Uppercase first char of a string Not quite; the last one (for ucfirst or \u) should be Titlecase, not Uppercase--which of course, are not always the same.

Re: [PATCH] perlipc.pod Revamp

2010-11-08 Thread Tom Christiansen
What the heck is this: Section 5 of the Fmodules file is devoted to Networking, Device Control (modems), and Interprocess Communication, and contains numerous unbundled modules numerous networking modules, Chat and Expect operations, CGI programming, DCE, FTP, IPC, NNTP,

Re: authorial perlipc edit

2010-11-09 Thread Tom Christiansen
Personally I really wish you had kept the changes to use lexically scoped filehandles. That's fine. I'm certainly not *against* lexically scoped indirect filehandles--except for all the extra syllababbles of English it takes to *mention* them:(--provided it doesn't complicate things or

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-03 Thread Tom Christiansen
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 perceived issues. Having real issues is quite distinct from

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-03 Thread Tom Christiansen
On Fri, Dec 3, 2010 at 3:56 PM, Tom Christiansen tchr...@perl.com wrote: We need to make it use strict friendly. No, we do not. =C2=A0Vide fricking supra. 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

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-04 Thread Tom Christiansen
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

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-04 Thread Tom Christiansen
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

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-04 Thread Tom Christiansen
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

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-04 Thread Tom Christiansen
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 snippet

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-05 Thread Tom Christiansen
Yes, I'm depressed too. I'm depressed that people are telling me that I don't talk good no more. That there is something about my language that isn't safe for the precious children to hear. That there are things one isn't supposed to do--not that they're illegal or anything, just that they're

Re: Current Issues with perlipc.pod - should they be fixed?

2010-12-06 Thread Tom Christiansen
The way I see it what happened was that I wrote an email with aspects of perlipc.pod that I found lacking, and not idiomatic up to recent best practices, thcrist replying that he doesn't like any of the changes and VETOing them (without saying why the status quo was better, just by giving