Title: RE: [IronPython] Road Map for IronPython
Closer to the former. Obviously, it's a highly
iterative project, so releases can easily build up functionality in whatever
order is important. Python projects with syntax highlighting would be easy.
IntelliSense is harder, mostly becau
Title: RE: [IronPython] Road Map for IronPython
I wouldn’t expect it to be.
But would it be a do-it-in-a month project, or a do-it-in-a-year-with-help
project?
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob Arnson
Sent: Wednesday, May 11, 2005 7:51
PM
To
Of
Keith J. Farmer
Sent: Wednesday, 11 May, 2005 10:28
To: Discussion of IronPython
Subject: RE: [IronPython] Road Map for IronPython
I think part of the question involved time? eg, 1.0 = next 6 months, next
year, ...
Incidentally, does anyone here have an idea of the difficulty involved in
I think part of the question involved time? eg, 1.0 = next 6 months, next
year, ...
Incidentally, does anyone here have an idea of the difficulty involved in
creating a language module for VS? Being able to create a .proj, have
access to intellisense, etc would be good for 3rd-party language
There's no published road map, but that's a frequent request and we need to do
something about that soon.
The plan is for IronPython to be fully CLI compatible which means that it
should run on the Common Language Infrastructure.
I think that you're asking about compliance with the Common Langu
