use Perl

I've finally packaged the Pexeso game as a CPAN application: Game::Pexeso. Now there are no excuses for not playing it!

The source code is available on github: pexeso git repo.

Remember that if you want your face to be in the game that you have to create a CPAN account!

The game is now on CPAN: Game::Pexeso.

Hopefully by the end of the week, if I get the time to package the game.

I was thinking of naming the package Game::Pexeso. What do you folks think of this? Any suggestions?

This certainly is covered in Damian Conway's PBP: "5.1. Lexical Variables Avoid using non-lexical variables."

I'm not referring to lexical variables (my), as you pointed out that part is covered by the best practices. I was referring to writing a single script from the top to the bottom with out localizing all variables. Remember that my only declares the variable for the life time of the current block. If the variable is not declared in a block then the file is the block scope, making the variable global. This is no matter if the variable is written in all caps or in lower case

I think that we have learned that declaring all variables as global is a bad programming practice. We are lucky with Perl that we don't need to do so. We can even declare our variables just before we need to. Other languages, C for instance, are not that lucky and are trying to address this in some way or another (C99 is doing it, a bit too late).

I like wrapping all my code inside a function, it limits the scope of the variables and doesn't allow me to cut corners. If I need something global it has to be pulled out manually from the block. Moving bits of code from the main function to another function is easier because if I forget a variable use strict; will spot it right away. Without this refactoring code that omits a variable will pass unseen as all variables are global.

You're right that I haven't chosen my words properly. I should have said scope discussion.

Please accept my apologies.

Chromatic as a good post on Declarations and Scope. I'm glad to see that I'm not the only one that follows this best practice. Which by the way I was surprised to not see in Damian Conway's Perl Best Practices.

I got confused because this is what I found with google: touchfreeze. I guess that I wasn't feeling lucky :)

The latest version of the MabBook Pro has no problem with the video camera. But under the latest MacbBook it doesn't work.

The missing CPU is not related to the kernel type. It's a well known kernel bug which causes the MacBook not to boot.

As surprising as it might seem the latest MacBookPro works better under Linux than the latest MacBook. A colleague has the new MabBoookPro and installing Ubuntu there was quite easy, when I tried to install the same OS in the MacBook I was set for a nice ride!

Definitely!

Cool but that program works on windows :( On the other hand the documentation says that it works like syndaemon on x-window! I should give it a try!

I use a MacBook as my main computer. I work on that laptop and do all my random hacking on it as well.

Log::Log4perl 1.25 has been released and it has two interesting enhancements:

• Color configuration and attribute support added to ScreenColoredLevels
• Patternlayout now supports %R, which returns the time elapsed from the last logging event

Thanks for the pointer! I will take a look at the program.

At the time I though one of writing a parser for C header files and XS files, but I didn't find a grammar module in CPAN that was convincing enough. Now that Damian Conway has released Regexp::Grammars I guess that the job could be easier.

Although, I did find an advantage in scanning the .so libraries. As it clearly shows which functions are made "public" in the C API. It's nice for finding "private" functions that haven't declared as static.

As I've said in my previous posts. I have two CPAN modules that provide bindings for C libraries.

One thing that I have I realized while I was writing these bindings is that sometimes C functions pass under my eyes unnoticed and that I forget to provide bindings for them. This can happen for various reasons:

• The C library failed/forgot to document some functions.
• New functions are added without being announced during the development.

I have in CPAN two modules that provide Perl bindings over two existing C libraries: Gtk2::Unique and Champlain. These two modules both wrap C libraries that use Glib's GObject framework. I don't want to go too much in the details of explaining how GObject works, so I will just keep it brief. What's important to know is t

I finally had the chance to resume my work on the Perl bindings for libchamplain which had a major release 0.4. The major change in this new version is the port to Clutter 1.0.