Comments for Perl Gerl

Comment on Will SWAG for food by perlgerl

perlgerl — Wed, 14 Mar 2012 10:33:14 +0000

At my current employer, France Télécom, we use yet another metaphor, the T-shirt scale.

Size: Days
ND 0 (non défini or undefined)
XS 0,25, 0,5 or 1
S 2
M 3
L 5
XL 8
XXL 13
XXXL more than 13

Comment on Getting Moose and Rose::DB::Object to play together by Rohan Almeida

Rohan Almeida — Thu, 13 Oct 2011 14:03:33 +0000

Yeah, my blog was compromised and unfortunately had to move the entire blog onto a new server. I still have a backup of my post but not the comments (which are the real stuff)

Comment on != by M W

M W — Tue, 27 Sep 2011 22:07:48 +0000

Yesterday I was struggling to figure out why Perl would not accept:

… it took me two minutes to realize that I really needed another cup of coffee.

Comment on Figuring out map coordinates by M W

M W — Tue, 27 Sep 2011 22:00:09 +0000

A fellow Perl+GIS user here. Thanks for all the tips!

Just found the Geo::Proj4 module, trying to write something to query EPSG’s database and return information about an EPSG code.

Comment on UTF8 follies by mjevans

mjevans — Wed, 13 Apr 2011 14:12:03 +0000

I’d be interested to see a small example of what you describe where it goes wrong. I use JSON::XS, DBI and hash keys with unicode values all over the place without utf8 and have never seen this. Could you post a small sample?

Comment on Started reading Perl Moderne by perlgerl

perlgerl — Mon, 11 Apr 2011 09:42:29 +0000

I haven’t got my copy handy, but off the top of my head I recall Eclipse/Epic, Padre, and the old geek standbys vim and emacs.

Comment on Started reading Perl Moderne by Gabor Szabo

Gabor Szabo — Mon, 11 Apr 2011 09:03:28 +0000

I am curious. What editors do they mention?

Comment on UTF8 follies by perlgerl

perlgerl — Sat, 09 Apr 2011 21:10:33 +0000

Tom, if I can keep one programmer from bashing his head on his desk, my life will not have been in vain.

Comment on UTF8 follies by perlgerl

perlgerl — Sat, 09 Apr 2011 21:09:54 +0000

Oh yes. I covered that base in my Rose::DB subclass:

__PACKAGE__->register_db(
…
connect_options => {
pg_server_prepare => 0,
pg_enable_utf8 => 1,
},
post_connect_sql => “SET CLIENT_ENCODING TO ‘UTF8′;”,
);

Comment on UTF8 follies by Belden Lyman

Belden Lyman — Sat, 09 Apr 2011 15:49:22 +0000

Another gotcha can be dumping UTF8 strings into postgresql and pulling them back out as gibberish. Tell DBI to preserve the UTF8ness:

DBI->connect(‘blah’, ‘blah’, ‘blah’, pg_enable_utf8 => 1);