This is the C::Blocks Advent Calendar, in which I release a new treat each day about the C::Blocks library. Yesterday I illustrated C::Blocks::Object::Magic while writing a simple class that had APIs in both Perl and C. Today I dig into one of the keys of yesterday's example: writing a type that can be used with C::Blocks.
Even more POD here on the Dist-Pen today.
I my last post I finally figured out how Pod::Weaver works, a template, weaver.ini file, that has 'Sections', [Name], [Author] etc, that you can change to create your POD document.
I wanted to test just how Pod::Weaver works so I replace '@default' in my 'weaver.ini' whith what the source code of Pod::Weaver::PluginBundle::Default said it was supplying;Hey everyone,
Following is the p5p (Perl 5 Porters) mailing list summary for the past week.
Enjoy!
On the day of the event, I reached the center at about 8:45 am with plenty of time to go through the registration procedure. I have been attending the London Perl Workshop for the last 4 years. But this year was little special as I was giving a talk, thanks to Neil Bowers. In fact he helped me prepare the notes and sharing his own experiences.
I was assigned "Room 2" for my talk. When I got there I realised that I didn't have the right connector to connect my laptop with the big screen. Dave Cross was also giving a talk in the same room and he suggested I talk to Mark Keating. Luckily, Mark had spare connector for me. I was sorted and ready to go. I still had 3 hours before my talk, so I attended the talk by Dave Cross about what new features added to perl.
Sometimes littlest bugs can really get on your nerves
Though not as much as the little critter above.
All started with a little module I wanted to upload to CPAN, well I did all the right things, test suite, manifest, makefile, POD coverage etc. I just wanted to do one test install on a clean box so I used my own Windblows PC.
Well it unzipped fine, passed its tests and installed with no problems. Great let see if it works
GitPrep v2.5 released today. Theme color become dark blue.
Let's try GitPrep example.
I'm going to implement "wiki" in next release!
Over the past couple months, I've had to take over project management for my DarkPAN project at $EMPLOYER, and the software they're enamored of for that purpose is JIRA.
Unfortunately, JIRA can be a pain in the ass sometimes, and since we're not the only group at $EMPLOYER that uses JIRA, getting things set up the way we need them is not always possible. However, it was possible to manually go through and fix up issues to our standards...
Well, whenever something is manually possible, I look for a way to automate it. I quickly discovered that JIRA has a REST API, so I went looking for a tool to help me use it in Perl.
I found JIRA::REST.
This is the C::Blocks Advent Calendar, in which I release a new treat each day about the C::Blocks library. Over the last few days I have illustrated how to use C::Blocks to write procedural code, how to get data across the Perl/C divide, including using types to do that concisely, and how to write code that is shared across modules and scripts. Yesterday I provided some benchmarks that I hope give a sense for the performance of C::Blocks, and start to indicate the circumstances when it might be useful. Today I am going to illustrate the many ways you can generate and/or modify your C code using C::Blocks including source filters, interpolation blocks, and the good old string eval.
It is still POD day here at the Dist-Pen
I spent the day trying to get a little deeper into POD::Weaver to understand how it works rather than just aping the three lines I have seen in the odd tutorial or should I say tuturial-ette;
[@Default]
[-Transformer / List]
transformer = List
Not faulting the documentation at all it is quite comprehensive and perfect if you are going to create a project like podweaver.
I'll state right off the bat that I have re-invented the wheel here. However, I did not know that until I asked on Perlmonks and was pointed to the resources that I couldn't find on Google. It was suggested on Perlmonks that a blog post, even for a re-invented wheel might be good, just for the purpose of getting the information out there. So, here it goes.
If you use the Devel::ptkdb debugger, then you know that one of its features is the ability to save breakpoints (and other info) in a *.ptkdb file that is reloaded the next time you run that debugger.
It's a feature I missed on those occasions where I needed to use the default debugger, not Devel::ptkdb. However, after scrounging around what docs there are on the default debugger, I was able to cobble together the following process:
1 - Create a file .perldb in your home directory and add this code
to it.
MetaCPAN is the community developed and maintained website and api for finding and learning about Perl modules. This year, we dedicated a long weekend to improving it and oh what a weekend it was!
Small problem solving day here in the Dist-Pen.
Just a quick post-ette today to resolve the problem I was having in my last post, where I was trying to get [PodWeaver] to work with 'Pod::Elemental::Transformer'.
I was trying to get this;
=head1 Table Of Contents
=for :list
* Database::Accessor::Tutorial::GettingStarted
* Database::Accessor::Tutorial::Basics
=cut
PerlModules.net is a website that notifies you when your favorite modules get updated, via e-mail or RSS.
As of today, you can now import your favorites from metacpan.org into perlmodules.net.
And if your metacpan favorites list changes in the future, no worries: the corresponding feed in your perlmodules.net account will adapt accordingly.
When managing code quality for bigger projects, SonarQube is the de-facto standard for many programming languages. Not for perl, as there has not been any perl integration into SonarQube yet.
We have Perl::Critic, a fantastic linting tool, but what if we could track our Perl::Critic issues in our projects over time? What if we had a webinterface where we could extract statistics about certain issue types? What if we could combine this with code coverage information? All this is about to come...
Come join me on my new open source project "sonar-perl": https://github.com/otrosien/sonar-perl -- I'm looking forward to it!
Just when you think the Dist::Zilla is gone, I am going to go back to the Dist-Pen for the next few posts.
I could just spend the next thirty posts or so writing up a new POD each day and posting the results here. I wouldn't learn anything though, I alreay know how to write POD, and I am sure I would loose any readers I might of gained over the last few weeks. So I think I will spare us that and instead re-visit Dist-Zilla today.
I am going to re-vist how I am using [PodWeaver] plugin, as I am facing some thirty POD files that will have a good deal of boiler plate in them and I would like to have some things just done for me.
To investigate how Pod::Weaver works I created only a single POD today 'Manual.pod' with just this in itHey everyone,
Following is the p5p (Perl 5 Porters) mailing list summary for the past week and a half.
Enjoy!
We had a great four days at meta::hack a couple of weeks ago. I've tried to briefly summarize what we accomplished.
blogs.perl.org is a common blogging platform for the Perl community. Written in Perl with a graphic design donated by Six Apart, Ltd.
