[kw-pm] kw-pm Digest, Vol 110, Issue 1

Raymond broadswd at gmail.com
Sat Sep 15 06:15:34 PDT 2012


Our production code is all C/C++ and uses make for compilation/linking, but Perl is the lingua franca for holding it all together, packaging, CI and production build systems, etc. Python is in there too but most new development is still Perl.
-----Original Message-----
From: Jung Myeng Lee <jm3lee at gmail.com>
Sender: "kw-pm" <kw-pm-bounces+broadswd=gmail.com at pm.org>Date: Sat, 15 Sep 2012 06:45:27 
To: Nick Dumas<nick.dumas at gmail.com>
Cc: <kw-pm at pm.org>
Subject: Re: [kw-pm] kw-pm Digest, Vol 110, Issue 1

> I do a fair bit of Perl at work.
> The official release stuff is C/C++/.net, but the prototype, debugging
> and "get whatever's left out of the corrupt file" stuff is Perl

I had similar experience at previous work place. I'm a C developer,
but I have written project configuration scripts, and cscope web
front-end in Perl -- they are still using it. There were tons of
legacy scripts written in Perl by others as well. A large silicon
vendor we had also exclusively used Perl scripts to configure their
system.

-- 
Brian Jung Myeng Lee
Homepage: http://koreanbrian.com
_______________________________________________
kw-pm mailing list
kw-pm at pm.org
http://mail.pm.org/mailman/listinfo/kw-pm


More information about the kw-pm mailing list