Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [eclipse-dev] What's happening after 2.1?

I wasn't actually suggesting C#/.NET support but why not?  With
a C# scanner/parser and a .NET code generation engine running
off the same internal representation as the Java compiler you'd
not only get C# support but be able to develop Java to run on
.NET and C# to run on a JVM too.

Dave Wathen
Phone: +44 (0)20 8660 5171
Mobile: +44 (0)7968 167934
Fax: +44 (0)870 051 7664
http://www.canzonet.com
mailto:dave.wathen@xxxxxxxxxxxx

-----Original Message-----
From: eclipse-dev-admin@xxxxxxxxxxx
[mailto:eclipse-dev-admin@xxxxxxxxxxx]On Behalf Of Hugh Spinks
Sent: 23 April 2003 00:59
To: eclipse-dev@xxxxxxxxxxx
Subject: Re: [eclipse-dev] What's happening after 2.1?


I'm desperate to see .NET/C# support. VS.NET absolutely sucks, especially
compared to Eclipse, but the .NET Framework is neat and if you're developing
Windows products...I know, I know...

Hugh Spinks
Sanford, NC

----- Original Message -----
From: "Dave Wathen" <dave.wathen@xxxxxxxxxxxx>
To: <eclipse-dev@xxxxxxxxxxx>
Sent: Tuesday, April 22, 2003 6:37 PM
Subject: RE: [eclipse-dev] What's happening after 2.1?


> If the suggestion is to get more ambitious I'd like to see the work on
> the 'Extended Java Family' extended towards support for generative
> programming.  By restructuring the compiler it should be possible to
> allow people to take greater advantage of it.  For instance the code
> generation back end could be reusable with different scanner/parsers
> generating ASTs from which .class files are generated.  More ambitiously
> the scanner could be opened up to support extended syntaxes and language
> embedding.
>
> I've attached a small document that outlines these ideas.  I can't see
> myself having the time to develop these ideas any further in the near
> future.
>
> Regarding the compatibility issues, could this be addressed - or at least
> mitigated - by producing adapter plugins that would allow 2.1 plugins
> to continue working.  This would fatten the footprint but could be an
> acceptable interim solution until plugin providers are able to migrate.
>
> Dave Wathen
> Phone: +44 (0)20 8660 5171
> Mobile: +44 (0)7968 167934
> Fax: +44 (0)870 051 7664
> http://www.canzonet.com
> mailto:dave.wathen@xxxxxxxxxxxx
>
> -----Original Message-----
> From: eclipse-dev-admin@xxxxxxxxxxx
> [mailto:eclipse-dev-admin@xxxxxxxxxxx]On Behalf Of Kevin Haaland
> Sent: 22 April 2003 21:10
> To: eclipse-dev@xxxxxxxxxxx
> Subject: [eclipse-dev] What's happening after 2.1?
>
>
> Late last year we posted an initial draft 2.2 plan which we were viewing
> as an incremental improvement over Eclipse 2.1. Now that we've started
> work on 2.2, we feel we should be setting even more ambitious goals for
> the next major release.
>
> We've put together a rough outline of what we'd like to tackle in this
> next release of Eclipse:
>
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/eclipse-project-home
> /plans/eclipse_after_2_1.html
>
> We'd appreciate community feedback to help us in firming up the next
> revision of the development plan.
>
> Please send your comments to the eclipse-dev@xxxxxxxxxxx developer mailing
> list.
>
> _______________________________________________
> eclipse-dev mailing list
> eclipse-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/eclipse-dev
>


_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/eclipse-dev



Back to the top