<code>
perl -lne '(1x$_) !~ /^1?$|^(11+?)\1+$/ && print "$_ is prime"'
</code>
Can I just say that testing for a prime number with one line of code is brilliant?
And it can run quickly too, the lower the divisor the faster the run time.
The algorithm however has some inefficiencies that will keep you limited to smaller numbers. It will scan to see if the number is a multiple of 2, then it will scan to see if it is a multiple of 3, then it goes on to scan for 4, which will never match because it would have stopped at 2. This inefficiencies of this algorithm cannot be overcome while using a regular expression.
However it is still really neat.
Hello all,
I am writing to advertise to all of you that Frozen Perl 2010 will be on Saturday, February 5-7, 2010. on the University of Minnesota campus Please register, come and have some fun with us.
We are also offering a hackathon on Sunday, and two classes on Friday one taught by brian d foy , and "Introduction to Moose" by Dave Rolsky.
The call for speakers is open and I'd like to see presenters from outside of our local PM group. Check it out and submit a talk.
If you are concerned about the weather in Minnesota in February, there is a hotel that is connected to our venue by underground tunnel: http://www.radisson.com/minneapolismn_metrodome. After you arrive, you won't have to go outside unless you choose.
Please pass this information on to your employers/co-workers/fellow students, as they might also like to attend.
If you or your business would like to sponsor Frozen Perl 2010, please contact me, or visit http://www.frozen-perl.org/mpw2010/sponsorship.html .
Thank you
Leonard Miller
Frozen Perl 2010 coordinator
My other goals were to have the sponsorship things ready to send, and to have my list done.
The sponsorship items are ready to send, and I have started sending them out to my list of sponsors. Last night I got through about 25% of my list. I think I will be able to finish off my list this weekend.
The next goals are to have the call for speakers completed this weekend, and to have a call for attendees written and ready to go by Wednesday next week.
The first goal was to get access to the website and learn enough about ACT to get the webpage up and running. I have done this, and I have sent the email off to have the test pages copied to the production website, so hopefully by the time you all read this Frozen Perl 2010 will be a working website.
The second goal was to have our sponsorship prospectus ready to mail out, and thanks to Drew on our planning committee, It has been completed and is ready to mail out.
My goal for next week is to have all of my sponsors contacted, and at least 50% of the rest.
This has been a productive week for Frozen Perl I hope to see you all here in February!
First, The original for our Sponsorship PDF has been lost so our graphic design person needs to re-create it, and so I wait.
Second I cannot log into the ACT servers any longer, and I don't really know why. Is it because my Private key doesn't match? was my account deleted? is there a server problem?). These same folks also need to create the conference in ACT. So I must patiently wait for them.
Third ... I haven't personally used ACT before, so I need to do some learning. However #2 prevents me from testing anything.
However there is a bit of good news I have a bit of help coming from Duluth from Ted, who answered my previous post where I asked for volunteers. (Honestly, I didn't expect anyone to answer that, so that was a pleasant surprise).
So, here I am patiently waiting for other folks to do their jobs. To be perfectly clear, no one is slow at this point, I just was not ready to have the problems that I am having.
Goals for next week:
1. have sponsorship letters OUT
2. Have access to ACT and have a preliminary FP10 website running (complete with registration).
3. have a start on the call for speakers.
Well, now I have a new hard drive in the mail, and I look forward to new hardware, and a chance to do some development with the community.
The root of the problem that they both say is that my talk might have driven new programmers from the community, but I don't understand how, as they never say exactly why.
Now before I go any further, I want to say that I will go over the talk very carefully if I ever decide to give the talk again. This is not about me not wanting to fix my stuff.
After my initial shock, I realized that they both went into how there were a lot of women in the audience and that makes it way worse, because I was going to drive them away from the community. I actually take offense to this on the womens' behalf. What difference does it make that there were women in the room? I don't want to treat women any differently than men. To do so would be patronizing, and make them even more aware that there are only 10 women in a conference hall with 300 other guys.
I feel that if you want more women in the community you need to talk to them and invite them to join. Don't treat them differently after they arrive. That is possibly the worst thing you can do.
I was really offended by the implication that I should have changed my talk, because the few women in our community were there, I mean really, either it is appropriate to give at YAPC, or it is not. The gender of the audience shouldn't change the content of a talk for YAPC. We are trying to be inviting to women and inclusive? Then invite them! The worst possible thing you can do is to treat them differently. Just thinking about it gets me pissed off on behalf of the women who were adventurous enough to attend a conference in a Male dominated field/subculture, just to be patronized by the same types people who review my talk.
The problem is that they might not even realize thier transgression, and that is the real problem. When talking with several of the YAPC organizers, and women programmers around my office, Everyone echoed the same things: That women don't want to stand out because they are different. Which means that changing a talk because there might be a woman in the room, is offensive. Either your talk was offensive to begin with (like the Ruby talk back in April), or because you are now patronizing the women who are attending your talk, treating them like beginners.
Anyone who says I should have fixed my talk because women were there. Shut up.
On the other hand, if you think I should fix my talk because I could have driven newcomers away from the community, I would like to listen to your constructive comments, because I don't have a recording of my talk, and therefore cannot review it myself.
I have gone on long enough about this, and I hope that I don't offend anyone, but this is how I feel on the topic.
/end rant
MST's badge 

Recent Comments