hello and this is one of my first scripts, which are not executable at present.
one year ago, there was no problem to use this script as shell-script (not yet in perl) like here :
#!/bin/bash
awk '{
for (i = 1; i <= NF; i++)
if ($i ~ /^SRC=/)
print substr($i, 5)
}' /var/log/syslog | sort -u | while read ip;
do
printf ' INVALID STATE ' && printf ' === %s ===\n' "$ip"
whois "$ip" >> log-002.txt;
done
I have used this script to filter syslog output after connections who are knocking on
the phone-lines ...
Now this script seems always to be stopped by the firewall of my provider. One year ago or 6 months ago this script was not stopped by third person (or program).
the output of today is the same like as one week ago:
INVALID STATE === fe80:0000:0000:0000:0a95:2aff:fe7a:bca7 ===
Is this the firewall of the provider stopping my script ?!
Thanks to the 14 people who attended and our three speakers, John, Peter and Mandy. Hopefully their slide decks will be available shortly.
In the "Good news everyone!" category, there are a couple of Perl shops in Sydney who are hiring right now (afaik, local not remote workers). People should feel free to ask after them via the Sydney.PM on Facebook page or the Email list
By popular demand, we will be convening again in December - speakers and a venue are all up for grabs. Use the above two links to volunteer.
It's that time again folks! Time to start planning for the DC-Baltimore Perl Workshop. I'm pretty sure we are now on year 5, and psyched to see everyone, old and new.
On behalf of myself and all of the workshop organizers, you are cordially invited to submit talks for the 2016 DC-Baltimore Perl Workshop, which will be held on Saturday, April 16, 2016, in Baltimore, MD!
As in previous years, by default talks are 25 minutes, which we've found is a sweet spot for most topics. We get a great variety -- enough to get a dose of newness and not overwhelm. We also welcome proposals for more tutorial-style talks of around 50 minutes. We'll take the talks and build out a two-track schedule.
I release Mojolicious::Plugin::AutoRoute. This is plugin which create route automatically. You can create web application with only writing template. It is understandable if you think This is plugin which embbed PHP featre to Mojolicious.
I've written my first Perl 6 module! I wanted to start contributing modules, but it took a while to find one that wasn't already done, but was simple enough to tackle as my first one. I also wanted to make a proper distribution for it, which was something I hadn't done before even in Perl 5, so it took a while to get everything in order. I'm sure there are still mistakes, but I'm still working on it, and it should go much better on future modules.
The distribution is at my GitLab repository. So far, it's just a simple wrapper around the 'ssh' command-line tool, which runs a command on a remote server and returns the output as an array of lines. I borrowed some of the code from the Perl 5 module Net::SSH, and Perl 6-ified it. It's not ready for panda or anything, but I hope to get it there once I make it more capable and add more error-checking and testing. A few observations:
I released GitPrep 1.11. You can install portable GitHub system into Unix / Linux easily. It is second major release.
Because you can install GitPrep into your own server, you can create users and repositories without limit. You can use GitPrep freely because GitPrep is free software. You can also install GitPrep into shared rental server.
Recently I have been working on this cool idea: using B::Deparse to help me figure out exactly where a program is stopped. This can be used in a backtrace such as when a program crashes from Carp::Confess or in a debugger like Devel::Trepan.
To motivate the idea a little bit, suppose my program has either of these lines:
$x = $a/$b + $c/$d;
($y, $z) = ($e/$f, $g/$h);
I might want to know which division in the line is giving me an illegal division by zero.
Or suppose you see are stopped in a Perl statement like this:
my @x = grep {$_ =~ /^M/} @list;
where exactly are you stopped? And would the places you are stopped at be different if this were written:
(Moved from reddit.com/r/perl now that blogs.perl.org seems to be behaving itself).
Over the past year or so I've had to deal with PPI for parsing and rewriting perl code a handful of times. Refactoring scripts are generally one-shot single purpose. Like any data mangling activity refactoring scripts can get messy because they're generally disposable, so architecture tends to be an afterthought at best. You can kind of tell this if you go and read Perl::Critic policies. They're plagued by boilerplate and repetitive code, and that's for code that is extensively reused. The problem multiplies in the case where you're writing throwaway code against PPI. In this post I'm going to show off PPIx::Refactor, which is a minimal interface to contain a small but annoying part of the mess.
I have started to create a list of programming exercises. Mostly extracted from my Perl beginner course. Some of them already have "Tools" that help solve the exercise. Some of them even have links to a solution in Perl 5.
My plan is to add many more exercises and to provides "Tools" and "Solutions" in Perl 6 and other programming languages as well. (Currently Ruby, Python and JavaScript are on the short list.)
If you have ideas for exercises I'd be happy to hear about them.
Do you use Dancer? Even if you don't, want to help one of the most awesome projects in the Perl community grow and reach a wider audience? You can, and you can get a copy of the book we're writing for helping us out.
Help the Dancer devs bring Dancer to a larger community, and help us get this book done. It will be a great resource for new and experienced developers alike.
I'm pleased to be sponsoring again this year as http://perl.careers/, but a reminder that the deadline for talks is end of this week, Friday the 6th of November!
If you'll just be attending but not speaking, by signing up early you'll make sure there's enough coffee and beer for you...
After this was written I received feedback from several respected members of the community alerting me to the problems that could be caused by is() *guessing* if it should be comparing numbers or strings. After hearing this feedback I agreed that the behavior constituted a bug, and one serious enough to alter the behavior post release. Test::Stream was marked *stable* recently enough that the change should not impact very many people, if in fact any.
The latest version of Test::Stream on CPAN no longer guesses if it is given a number vs a string.
In the very near future cmp_ok, and a 'Classic' bundle which provides just the functionality of Test::More, including classic 'is' and 'is_deeply' will be released, and will be the recommended bundle for people moving from Test::More. Branches and pull requests for both of these have been written, I am giving them some time for review before proceeding with their release.
[This is a post in a new, probably long-ass, series. You may want to begin at the beginning. I do not promise that the next post in the series will be next week. Just that I will eventually finish it, someday. Unless I get hit by a bus.]
Last time I went into more details about how I might go about creating a new date module, and what I would expect it to achieve. This time we clear out some housekeeping and try to nail down a design strategy.