NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
The past revisited. Again. (Score:1)
Re:The past revisited. Again. (Score:2)
Surely there is more to CLR and .NET than just that. Or has the idea of a "compatible calling convention" simply been upgraded to include method calls, object definition, versioning, cryptographic signatures and reflection? And do you really need to have a VM for all of that?
Reply to This
Parent
Re:The past revisited. Again. (Score:1)
All the other stuff is either upgraded calling conventions (method calls, reflection) or fancy dynamic loader stuff (versioning, crypto signatures). And no, you don't need a VM for it at all. You can do it entirely as normal, compiled code.
The single biggest hurdle is the initial definition of the conventions, and that's as much engineering tr