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
ednesday, May 11, 2005 3:56 AM
To: users-ironpython.com@lists.ironpython.com
Subject: [IronPython] Road Map for IronPython
Hi All,
Is there any published Road Map for IronPython ? Will it be fully CLI compliant
?
I understand that using Enum type as bit field is not currently supported and
will be done f
Hi All,
Is there any published Road Map for IronPython ? Will it be fully CLI compliant ?
I understand that using Enum type as bit field is not currently supported and will be done for v0.7.5 release. Similarly, what about other features that we have in C# ? Any document available which general
