From PerlNet

Hi, feel free to add any messages for me on this page.

I did the [[Category:Melbourne.PM Users]] thing

Alec 16:03, 19 January 2006 (EST)

And now I did the Nickname thing as well.

Thanks

Alec ^(talk) 22:44, 19 January 2006 (EST)

Contents 1 Re: New Pages (http://perl.net.au/wiki/User_talk:Raphael) 2 Mock Object example up 3 coverage testing reports 4 continue help for jbt 4.1 for example 4.2 An example by PJF 4.3 I'm not too happy with the modifications to "Perl Myths" 4.4 Please stop Stepping on Contriubtors' Toes 4.5 re: User talk:66.215.57.61 4.6 Whitelisting My Account (and Possibly Others) From the Captcha 4.6.1 Done!

Re: New Pages (http://perl.net.au/wiki/User_talk:Raphael)

Thanks Jacinta,

I'm thinking it's about time to do that, I want other to feel free to contribute too.

Thanks for watching out for us!

Raphael

Mock Object example up

I rushed this out - hope its ok

L --Leriksen 16:19, 3 February 2006 (EST)

coverage testing reports

I have some html-format reports from Devel::Cover, that may be useful to add into the testing tools discussion.

They show some code in a fairly early stage of development, so there is code ranging from 20% to 90% coverage.

There are 29 html files (largest is 38k, most in the 2-6k range), one 2k css file and one ".12" file that is 6k and I have no idea about.

Is it possible to place these in a wiki env ? It may be helpful to have reports from D::C that are navigable.

Leriksen

continue help for jbt

  while (EXPR) {
         ### redo always comes here
         do_something;
  } continue {
         ### next always comes here
         do_something_else;
         # then back the top to re-check EXPR
  }
  ### last always comes here

that's the exact sample on perldoc which unclear to me

for example

  my $line_count = 0;
  while (<>) {
       next if /^$/;   # skip blank lines
        
       last if /^q$/i' # stop if line is Q or q (quit)
        
       # do some stuff
  }
  continue {
       $line_count++;
  }
   
  print "Walked through $line_count lines.\n"

An example by PJF

  my $i = 0;
  
  while ($i < 10) {
     next if $i % 2;       # Skip odd numbers.
     print "$i\n";         # Print my number.
  } continue {
     $i++;                 # Always increment $i
  }

This could also be written (without the continue) as:

  my $i = -1;              # Start at -1, since we'll increment
                           # at the start of each loop.
  
  while ($i < 10) {
     $i++;
     next if $i % 2;
     print "$i\n";
  }

or using a for loop:

  for (my $i=0; $i < 10; $i++) {
     next if $i % 2;
     print "$i\n";
  }

I'm not too happy with the modifications to "Perl Myths"

Hi Jacinta!

Thanks for your great contributions to Perl in Australia, and on this wiki.

As you know, I started writing the Perl Myths article, and you have completely changed it in one fell swoop. Since I felt that I could not handle such a drastic page, I reverted it, but you re-reverted it. I'm not too happy with the "Perl Myths" article as it is reading now. I find it too direct, annoying and laconic. I wouldn't call it better. I could fork my own copy and move it to a different wiki, but I'd rather not.

As much as I appreciate the power of wikis, I hate having a livelock like that, and think that articles are best done with one or few contributors.

User:Shlomif

--06:09, 28 April 2007 (EST)~

Response: User_talk:Shlomif#Perl_Myths_page

Please stop Stepping on Contriubtors' Toes

Hi Jacinta!

As I noted earlier, I was distressed about you editing the pages I started contributing to en masse, and transforming them into resources I did not have in mind. Well, it seems it happened with you reverting my revert to Perl Myths and yet again with transforming Perl 6 - Common Criticisms into a Perl-6-hype+Perl-5-FUD page instead of the more objective and well-rounded page that also gave some common arguments against Perl 6 (and their rebuttals), that I had in mind when I started working on it.

Despite the fact that Wikis are world-editable, there is such a concept of propriety in them. Imagine if you headed a medium or large scale open-source project and suddently received a huge patch that did something drastic (like changing words_separated_by_underscores to studlyCapWords), without you being able to understand whether it breaks the code or not? Obviously you will reject this patch. I want to contribute to the wiki, and have some control of my articles, rather than them being edited en masse, and led to directions I'd rather they not take, and that I need to clean up afterwards.

If you want to do changes, either change them incrementally, or comment on them in the discussion page.

Regards,

User:Shlomif ----03:36, 12 May 2007 (EST)03:36, 12 May 2007 (EST)~

Response User_talk:Shlomif#Perl_6_-_Common_Criticisms

re: User talk:66.215.57.61

> It seems that you've recently had some difficulty with the #perl channel on Freenode, and I'm sorry to hear that.

Some difficulty would be an understatement.

>Unfortunately you won't change channel policy by changing the FAQ hosted at this website.

I totally agree with that -- you can lead a horse to water, but can make him pull his head out of his bum.

>Perhaps you could join the #perlnet channel on freenode instead. It's much smaller and is often only active during Australian business hours but we might be able to help you with whatever problems you're having.

Now that would have been fine had they left it that way, but no. Rather they not only did a complete domain lock out on the #perl channel, but also on the #perlcafe channel. Which it should be noted that if you insult me, I say "g'day" to you and put you on ignore why do you get to be offended?

Now I have no need wish to change any policies (although it would be interesting if people actually stuck to them for everyone). However, as this site is listed as the faq place to go as per the channel it may be opinioned that this was way off:

Chris62vw

... He is rather hands-off when it comes to policing the channel and believes in minimal usage of operator privileges. ...

As such with wiki pages, all kinds of people come by and make changes where incorrect information may be noted. If this was not wanted or allowed options like the edit feature would not be available. As well, it would only seem fair to new #perl and #perlcafe users to give them a bit of a heads up on this issue and state that a bit of submissiveness is required.

Oh, on another note if someone goes into a channel asks a question without $nick: and someone sees it but doesn't like it or know it or whatever, they don't have to reply to it. I know, so simple.

Anyway I'm off to find how to perl for irc.

All the best,

Whitelisting My Account (and Possibly Others) From the Captcha

Hi!

As User:Shlomif I have made many contributions to the wiki, and recently been editing the Tom Limoncelli interview transcript. I've seen that now a mathematical Captcha is required for every edit to the pages. It's become annoying for me to fill in the captcha for every edit.

Would it be possible to whitelist my account ("Shlomif") from the captcha, and possibly some other accounts of trusted users, so we won't have to do the captcha for every edit when we are registered?

Thanks in advance.

Shlomif 20:57, 20 October 2007 (EST)

Done!

PJF will take care of this.

Jarich 22:30, 24 October 2007 (EST)