1. I asked for them back in the 1980s. But I am only one bleeding edge Ph.D. CS guy, so no one listens to me.
2. I am impressed with the current level of Visual Basic support (which, while not being as dynamic as Python, does have late binding). Is there a roadmap as to when and how deeply Python support in VS Studio will be. I.e. when will Python be as baked-into VS Studio & .NET framework as VB currently is? (or perhaps an easier way of asking & answering - what will still be missing when VSstudio 2008 and .NET 3.0 (or 3.5) is released). From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Curt Hagenlocher Sent: Wednesday, October 24, 2007 9:05 AM To: Discussion of IronPython Subject: Re: [IronPython] dynamic languages and .net 1.0 On 10/24/07, David Jensen <[EMAIL PROTECTED]> wrote: A small question. I assume .net support for dynamic languages, interpreters, reflection was not in .net 1.0. Microsoft started as a compiler company and I thought Bill Gates was strongly in favor of interpreted languages. I thought it was odd that Microsoft apparently did not supply interpreted languages in .net 1.0. Is this because "reflection?" was more difficult to implement or were interpreters a lower priority? Reflection was fully baked in the initial release of .NET. Microsoft is pretty good at implementing what its customers are asking for, though obviously they can't achieve instant turnaround. Don't be misled by the current popularity of dynamic languages; when the CLR was being designed ten years ago, it's likely that none of Microsoft's customers was asking for them. -- Curt Hagenlocher [EMAIL PROTECTED]
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
