Just another quick test postette day here in the Moose Pen.
As we seen in this post I found a bug where I was not coercing correctly on deeply nested Element Attributes. So that means back into the test suite of Database::Accessor I go to cover that bug and the new recusion functionality I have added recently.
Checking the current state of the test suite I see that I never did go deeper than one level of elements, though I do check to ensure that the View on elements are correct and the correct Class is passed in. Howeve I only test for Param and Element classes now I have at lest two others to check for.
I decided it is best to go for broke and create one have that will cover I think all of the combinations I could think of. Here is the hash;
In the time while I was thinking about what I should write about Bailador a new Github Issue was created. So I changed my mind...
Actually I just wanted to let you all know that I've released version 0.0.8 of Bailador today. I wanted to show you the Changelog and maybe I wanted to explain a few bits. I could've talked about Github Issue #169, because it appeared to be more work as I thought at first glance. I realized that some parts of the code in Bailador::App and Bailador::Route could be better and during refactoring I stumbled over https://rt.perl.org/Public/Bug/Display.html?id=131707. After all I am hoping that I have left the code in a better state and the behaviour of Bailador is now more reasonable and consistent.
I got a fantastic opportunity to give a talk at Barcelona.pm meetup in August. I'll speak about The Perl Foundation, focusing on grants and donations. For those who love technical talks as much as I do, there will be three more interesting talks by other Perl Mongers.
I started learning Spanish using Lingua::ES::Numeros. Uno, dos, tres. ¡Buenas tardes a todos!
Over the past few days I have made up quite a few tests and they where all the same pattern
Base hash
add function/expression element
create DA
run select/retrieve
check SQL
check parms
so a little re-factoring is in order me thinks., Though there is a school of thought that it is a waste of resources to re-factor working test. Fortunately I do not ascribe to that thought so here we go.
The re-factoring was quite simple, I took my test;
The Dancer Core team has just released Dancer2 0.205001. This release primarily fixes some documentation issues with a couple of notable exceptions:
If HTTP::XSCookies is installed, Dancer2 will check at install time to see if the correct version is installed (Peter Mottram)
Dancer2 is now tested by Travis CI on Perl versions 5.22, 5.24, and 5.26, as well as Appveyor (Dave Jacoby)
All reference checking under the hood is handled by Ref::Util (Mickey Nasriachi)
We have several new contributors this release. Thanks to Dave Jacoby, Abdullah Diab, Glenn Fowler, and Jonathan Cast for your first patches to Dancer2!
The bug report described that in some cases, when the user searched
for an edit distance with Unicode strings, the user's input value,
$string in the following, seemed to be being overwritten and
corrupted:
$tf->distance ($string);
I couldn't reproduce the user's bug using the script he supplied, but
just in case, I went through the code and tried to find anywhere that
a string might be being overwritten, by adding const in front of
every char * pointer which was used to store a Perl string.
This led me to this
line
where the value corresponding to $string in the above is read using
SvPV, and this
line
where the value pointed to is overwritten by the code. This is a
special case which only executes when the user matches a byte string
against a character string.
Now that I have 'Functions' nicely working I am going to move on to the next logical field and that is an 'Expression'. In SQL (and 99.9% of other languages) an expression is just a predicate that can be evaluated. So an SQL like this
SELECT user.username, user.salary + 10 FROM users WHERE username='BOB'
In Database::Accessor I have an Expression class for this and it works 90% the same as the Function class I just finished. Thus this expression;
I put out a notice not long ago that I was contemplating writing a guide to using the Raspberry PI with Perl.
One person who pointed out one minor mistake of mine with follow up with some other questions, asked about how to run a servo without needing a controller board. I realized that I hadn't exposed a couple of functions in the core WiringPi::API distribution that allowed a user to configure the PWM frequency, which is required as the Pi default doesn't play nice with typical servos.
The default PWM base frequency on a Pi is 19.2MHz, which is then divided by the clock signal (default: 32) and the PWM range (0-1023). So to get the default operating frequency:
# base range clck operational freq
19.2e6 / 1024 / 32 == 586Hz
This article represents my own thoughts on the matter alone and is not an
official statement on behalf of the Rakudo team or, perhaps, is not even
representative of the majority opinion.
When I came to Perl 6 around its first stable Christmas 2015 release,
"The Name Issue" was in hot debate. Put simply: Perl 6 is not a replacement to Perl; Perl 6 is not the "next" Perl; Perl 6 is a very different language
to Perl; so why does it still have 'Perl' in its name?
From what I understand, the debate raged on
for years prior to my arrival, so the topic always felt taboo to talk about,
because it always ended up in a heated discussion, without a solution at end.
However, we do need that solution.
Browsing the puny (I miss Borders!) Technology section at the local Barnes & Noble today, I did not see a single Perl book. I was hoping that they sold out, but the manager confirmed my fears: they no longer carry Perl books in that store. The reason, he said, is that no Perl book has been published since 2012.
In regard to the size of the Technology section: The way the shelves are stocked is based on sales. Since people rarely buy their technology books from the store (guilty...), the Technology section is correspondingly small. "The people who are interested in these books read them in the Cafe, but they never buy them."
Escaping HTML is the process of converting a user's input into something which can be displayed back to the user in a web browser. For example, in a comment section on a blog, or a wiki editable by users.
Given user input such as <script>, to display that correctly, an HTML
escaper must output <script>. This is then converted into
<script> rather than an actual HTML script tag by the browser:
s/</</g;
s/>/>/g;
But supposing the user inputs <script>, what should be done with it?
If the <script> is not altered by the HTML escaper, then when it is displayed back to the user, it gets converted by the browser back into <script>, which is not what was intended, and even worse if the user tries to edit the comment again, the HTML tag may get removed from the text.
The solution to this problem is to also convert the ampersand, &, into an HTML entity, like this:
I've been working on the CPAN Testers project since 2015. In all that time, I've been focused on maintenance (which has involved more operations/administration tasks than any actual code changes) and modernization. It's that modernization effort that has led to a new CPAN Testers API.
Its get back into Driver::DBI day today here in the Moose-Pen
I decided to get a little more ambitious and see it I can get Driver::DBI to handle a function call in an SQL select, like this;
SELECT user.username,
left(user.username,11),
user.address
FROM user
WHERE user.username = 'Bill'
The way I have planned to do this is Database::Accessor with the 'Function' class, which has a simple string attribute for the function name and it is used with 'Comparator' role attributes. Thus I can break
This is the second part in the series! Be sure you
read Part I first where we discuss
what Seqs are and how to .cache them.
Today, we'll take the Seq apart and see what's up in it; what drives it;
and how to make it do exactly what we want.
PART II: That Iterated Quickly
The main piece that makes a Seq do its thing is
an object that does the Iterator
role. It's this object that knows how to generate the next value, whenever
we try to pull a value from a Seq, or push all of its values somewhere, or
simply discard all of the remaining values.
