Which version of perl should i use

Like Windows, ActiveState has a free community edition for developers. The Windows caveats above apply, except for a current Perl version 5. Your best bet is to install the Homebrew package manager in the macOS Terminal application after installing its requirements , and then issue the command brew install perl. This will install the latest version of Perl, as well as give you instructions for making sure that installed Perl modules stay that way across updates by Homebrew.

Also like macOS, these are usually older versions provided for compatibility with other software provided by the OS.

To install your own on Linux, you can go the ActiveState route as above, or also use the Homebrew package manager. There are several requirements to install first , and then you can follow the directions for installing Homebrew and issue the command brew install perl.

You can download it directly and build a version yourself, after installing any prerequisite packages used to build software on your operating system see below. However, most Perl developers choose to use a tool to automate that process and manage different versions of Perl side-by-side. Enter perlbrew. It no longer is. Go with 5. There's many, many bug fixes in it that you WANT.

I have had no hesitation in recommending it [Strawberry perl], since I discovered it via the esteemed brethren herein. A user level that continues to overstate my experience :- [reply] Re: Which Perl version shall I use? Installation is as easy as ActivePerl and has the option to install lots of cool extras - like tools needed to compile other libraries. While you didn't mention it, I thought I'd suggest the perl distribution in the Cygwin environment.

But since it lacks all the frills, bells and whistles on other distributions, you'd be happier with another distribution.

Since Cygwin also has compilers and such available, I find that most modules install with CPAN and no particular effort. In those systems, I just copy the tarball over and use the standard:. Problems installing new Modules for ActiveState v 5. If you're producing code for yourself you can be experimental and do whatever appeals to you.

If you're producing Perl versions and code for, say, Windows based laptops and have very little time to do it in, then already assembled packages and ease of installation factor in a great deal. This is especially true if you're going to support it all after the installation, and perhaps even more so if you eventually intend to pass off the support to someone else.

Hello All, If I am not wrong current version of Perl is 5. This way, you do not need to purchase a Visual Studio license to cover the running of Visual Studio on the build server for each person whose actions initiate a build.

On our team, we don't actually have VS installed on our build server and are able to compile code and run unit tests, but you'll probably find it pretty straightforward to just install the 'highest' version of VS that your team has a license to just to keep it simple and not waste any time tracking down any issues.

Which version of Perl should I use on Windows? Asked 5 Months ago Answers: 5 Viewed 47 times. Try from command prompt: assoc. You are allowed to install Visual Studio on the build server without an additional license. You may or may not choose to follow this usage. But never write "PERL", because perl is not an acronym. He previously used the phrase with many subjects "Just another x hacker," , so to distinguish his JAPH, he started to write them as Perl programs:.

Other people picked up on this and started to write clever or obfuscated programs to produce the same output, spinning things quickly out of control while still providing hours of amusement for their creators and readers.

Appeal to their self interest! If Perl is new and thus scary to them, find something that Perl can do to solve one of their problems. That might mean that Perl either saves them something time, headaches, money or gives them something flexibility, power, testability.

In general, the benefit of a language is closely related to the skill of the people using that language. If you or your team can be faster, better, and stronger through Perl, you'll deliver more value. Remember, people often respond better to what they get out of it. If you run into resistance, figure out what those people get out of the other choice and how Perl might satisfy that requirement. You don't have to worry about finding or paying for Perl; it's freely available and several popular operating systems come with Perl.

Finally, keep in mind that Perl might not be the right tool for every job. You're a much better advocate if your claims are reasonable and grounded in reality.

Dogmatically advocating anything tends to make people discount your message. Be honest about possible disadvantages to your choice of Perl since any choice has trade-offs.

Copyright c Tom Christiansen, Nathan Torkington, and other authors as noted. All rights reserved. Irrespective of its distribution, all code examples here are in the public domain. You are permitted and encouraged to use this code and any derivatives thereof in your own programs for fun or for profit as you see fit.

A simple comment in the code giving credit to the FAQ would be courteous but is not required. Please contact him via the GitHub issue tracker or email regarding any issues with the site itself, search, or rendering of documentation.

The Perl documentation is maintained by the Perl 5 Porters in the development of Perl. Please contact them via the Perl issue tracker , the mailing list , or IRC to report any issues with the contents or format of the documentation.