Timm Murray

• About: I blog about Perl.

Recent Actions

• Posted Video Encoding Modules? to Timm Murray

  I'm putting the final touches on UAV::Pilot v0.3, which will have a better event-driven API and support control through Joysticks and (maybe) Wiimotes.

  This brings me to the point on the ="https://github.com/frezik/UAV-Pilot/blob/mas…

• Posted Announcing: UAV::Pilot v0.2 to Timm Murray

  UAV::Pilot, a library for controlling UAVs like the Parrot AR.Drone, has now released version 0.2. Details on my blog.

• Posted Announcing: UAV::Pilot v0.1 to Timm Murray

  UAV::Pilot is a Perl library for controlling UAVs. It currently works with the Parrot AR.Drone, with plans to expand to others in the future.

  Demo video

  The current library supports basic commands, such as takeoff, pitch, ro…

• Commented on SQLite and Writes
  Whatever you want to call it, I still don't think it's a good way to do things....
• Posted SQLite and Writes to Timm Murray

  Most DBI tutorials will show you how to use prepare()/execute(). Something like this:

  my $sth = $dbh->prepare( 'INSERT INTO table (foo, bar) VALUES (?, ?)' ) or die ...;
  $sth->execute( 1, 2 ) or die ...;
  $sth->finish;
  

• Commented on On the version number succeeding Perl 5
  There was a Java 2. It was version 1.2, and it was where Sun put in all the stuff they intended to get done for the first version but ran out of time. Anyway, I agree with the basic premise,...
• Commented on Perl 5 Porters Weekly: September 3-September 9, 2012
  At this point in Perl5's history, is there really much use for prototypes? Everyone has more or less settled on using a hash(ref) for named parameters, and this proposal seems to only cover positional parameters. It's at least ten years...

Comment Threads

• Ether commented on On the version number succeeding Perl 5

  “Breaking” backcompat in the sense of disabling certain syntax by default but still allowing it to be used if options are set: fantastic! To no indirect I’d add no bareword::filehandles and no multidimensional.

  Wait, isn’t that what use strictures does, which is used by Moo? hmmmm… :)

• Toby Inkster commented on On the version number succeeding Perl 5

  strictures.pm also enables fatal warnings. There are some warnings I’d never want to be switched on by default, let alone fatal by default.

  (I’m thinking mostly of uninitialized, void and once, but also to an extent numeric.)

• tommolesworth.myopenid.com commented on SQLite and Writes

  Useful information, thanks for that.

  Is there any particular reason for the manual error checks on each step rather than setting the RaiseError flag? (this modified version of 02_busy.t seems to indicate that it throws an error as expected, on first read of your post I thought you were talking about an "invisible" data loss situation)

  Also, switching to mysql (or other DBs) won't help much here, there's still the chance of deadlocks - see ="http://stackoverflow.com/questions/2596005/working-around-mysql-error-deadlock-found…

• cbt commented on SQLite and Writes

  This is why, when I have an app that uses sqlite, I jump through hoops to avoid opening it more than once. I put blocking 'flock' calls in the 'open' method of my database class. And I have it print a big fat warning message if it blocked. If I have a brain fart and try to open more than once, I get a loud early warning. Before I've caused any failed database updates.

• Ether commented on On the version number succeeding Perl 5

  I can see not wanting some warnings to be fatal, but it’s so rare to need to disable certain warnings entirely (e.g. numeric) that I’d be firmly on the side of keeping them enabled.

  Another change one could make in such a release is to do all the things tchrist lists as needed for full unicode and utf8 compliance: http://stackoverflow.com/a/6163129/40468