为什么没有IronPerl（Perl的用于.NET）？ [英] Why is there no IronPerl (Perl for .NET)?

问题描述

我有点失望的是，似乎没有要任何的努力，使Perl的.NET世界的一等公民。

I'm a bit disappointed that there doesn't seem to be any effort to make Perl a first-class citizen of the .NET world.

我读过，在过去的几个'原因'，但我不明白他们为什么不能克服的（不同的垃圾收集器，难以解析语法的CPAN模块的一部分不能被移植，不同的社区，...）。

I've read a few 'reasons' in the past, but I don't see why they can't be overcome (different garbage collectors, hard-to-parse syntax, part of CPAN modules couldn't be ported, different communities, ...).

ActiveState公司有 Perl.NET 的产品，但它是一个黑客（以良好的意识）围绕一个标准间preTER和一些语法糖进行互操作.NET程序集。

Activestate has a Perl.NET product but it's a hack (in the good sense) around a standard interpreter and some syntactic sugar to interoperate with .NET assemblies.

几年前，他们停止了Visual Studio集成的Perl的理由是缺乏兴趣。这是前一段时间，之前的所有更改，.NET，使之更动态。

A few years ago they stopped their Visual Studio integration of Perl citing lack of interest. That was a while ago, before all the changes to .NET to make it more 'dynamic'.

我是唯一一个谁渴望 IronPerl

推荐答案

我觉得你的痛苦。有很多次，我一直希望在.NET Perl的功能，特别是当它涉及到文本类型的文件。不过，我很幸运的是，口头禅合适的工具合适的工作，已经让我使用Perl处于最佳状态，而不用担心其集成到.NET应用程序。

I feel your pain. There are plenty of times where I've wished for Perl's features in .NET, especially when it comes to text type files. However, I've been lucky in that the mantra 'right tool for the right job' has allowed me to use Perl at its best, and not worry about integrating it into .NET applications.

编辑：有草莓的Perl 已经远远一种恩赐给我，并让我从我的应用程序调用最Perl脚本需要时，而不用担心直接集成。

Having Strawberry Perl has been far more of a boon for me, and allowed me to call most Perl scripts from my Applications when needed, and not worry about direct integration.

这篇关于为什么没有IronPerl（Perl的用于.NET）？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！