![]() | This article is rated Start-class on Wikipedia's
content assessment scale. It is of interest to the following WikiProjects: | ||||||||||||||||||||||||||
|
Common language infrastructure (CLI)is a term which gives no results when run on the Microsoft web site]. But Common language runtime is not much better (4 hits). And Common language runtime gives a lot of hits, but they seem to be Java related.
A general google search on Common Language Infrastructure and Common Language Runtime gives a considerable amount of results. But sorting out needs its time.
I would like to see an article which translates the Microsoft speak into commonly known computing terms. The stub above is a first attempt at this. Perhaps it should be moved to another heading. -- Kwaku
CLI as seen with the eyes of a Java proponent: http://www.javalobby.org/clr.html (link put here to consult for further work on the article)
I removed some stuff because it was copied without even some decent formatting from http://hosting.msugs.ch/dotnetrox/vb/Ch01.html -- Jan Hidders 20:47 Sep 7, 2002 (UTC)
One of the strengths of CLR seems to be that it allows lots of different languages to be integrated and call each others' code. The code to produce and use DLL assemblies in many languages is quite simple. Is there any similar "inter-language integration" layer in Linux, or in the open source world? I have used SWIG and Boost, however, I'm more asking whether it is possible to not merely export C++ code into various languages, but rather, to share code between pairs of arbitrary languages. For example, is it possible to take a CPAN Perl module and call it from Python, or export a Tcl module and a Ruby module and call each of these from clisp? If the necessary technology to do this does not exist, then I'd like to know that as well. Thanks. Connelly 00:08, 21 July 2006 (UTC)
I noticed that the article has no category. Maybe separate Category:Microsoft .NET should be created? -- Derbeth 19:42, 3 Apr 2005 (UTC)
My understanding is that the CLR (Common Language Runtime) is not technically a virtual machine. It does not run IL code, it loads and compiles it. The architecture is designed to provide a platform-neutral layer similar to that provided by Java's Virtual Machine, but the mechanism is different.
I've repositioned the implementations section to logically follow Standardization and Licensing. A question regarding MS .NET FW there: why is it called 'commercial' if it's available for free download? -- tyomitch 08:45, 2 September 2005 (UTC)
I'll address this on the project page, but the CLI is a spec, and the CLR is an implementation of CLI plus libraries, etc., so it makes more sense to put the implementations in the CLR article. -- Foofy 18:12, 4 October 2005 (UTC)
Can we get some more information about the patents held on the Common Language Infrastructure? They're pretty significant for projects like DotGNU and Mono. Is there a chance these projects will one day be attacked my Microsoft and forced to stop? Herorev 00:26, 23 September 2007 (UTC)
There is still a lot of doubt over/room to misinterpret the CP, especially regarding Mono. The absolute statement that programming with it has been made completely safe is anything but definite, and should probably have a dubious tag. C# for instance is only protected by the standard for an older implementation, and the CP doesn't include quite a few things, like Windows Forms, needed for some functionality. Raider480 07:57, 14 October 2012 (UTC)
While Microsoft and their partners hold patents for CLI, ECMA and ISO require that all patents essential to implementation be made available under "reasonable and non-discriminatory (RAND) terms."
does that sentence make sense? —Preceding unsigned comment added by 201.152.52.113 ( talk) 08:51, 11 December 2007 (UTC)
The page Common Language Specification linked to in the Overview has only the same information as the Overview's paragraph. Should the page be removed, with a redirect to the Overview? Also, should it have an inline link to MSDN's page on Common Language Specification and/or the link in the References section? Tagus ( talk) 05:45, 16 August 2009 (UTC)
"No Support For" is a bit misleading? Iron Python is a CLR implementation of Python, which is a Dynamic typed language. So I guess you don't need support for dynamic typed languages in order to support dynamic typed languages.
Whatever. It just doesn't seem like a clear statement. —Preceding unsigned comment added by 203.206.162.148 ( talk) 07:35, 11 January 2010 (UTC)
The page should mention the relationship between CLI and CLR.
Encyclopedant (
talk) 19:58, 1 January 2019 (UTC)