Re: D compiler for .NET

2009-06-11 Thread Tim Matthews

Jason House wrote:
Earlier today, I tried to use the D compiler for .NET from 
http://dnet.codeplex.com/


Beyond compilation of the compiler, I found zero instructions on what to do 
next.  How do I integrate the compiler into the .NET framework/visual 
studio?  I'd like to be able to add D files to existing solutions (with C# 
code).  If I can do that, I'll probably push for some small adoption of D at 
work.  (I'm hoping mixins and templates will inspire the initial use of D)


Any tips or documentation on how to get started would be appreciated.



It works from the command line like dmd but with ms vs tools like ilasm 
in your path too. Visual studio could probably make use of it but is 
there any D VS plugin projects that are not dead?


It uses D import files to call existing clr code but it only has a few 
things in the import files. It is possible to add stuff to the import 
files but the plan is to generate the imports automatically. It is 
pretty much very experimental at the moment and could do with the extra 
man power to get it going. Dmd front end in source control with proper 
documentation as you asked in D newsgroup would help a lot.


The import generator is mostly working but the generated imports are not 
parseable. http://d.puremagic.com/issues/show_bug.cgi?id=3061


Re: D compiler for .NET

2009-06-10 Thread Jason House
Daniel Keep Wrote:

 
 
 Jason House wrote:
  Earlier today, I tried to use the D compiler for .NET from 
  http://dnet.codeplex.com/
  
  Beyond compilation of the compiler, I found zero instructions on what to do 
  next.  How do I integrate the compiler into the .NET framework/visual 
  studio?  I'd like to be able to add D files to existing solutions (with C# 
  code).  If I can do that, I'll probably push for some small adoption of D 
  at 
  work.  (I'm hoping mixins and templates will inspire the initial use of D)
  
  Any tips or documentation on how to get started would be appreciated.
  
 
 The back-end code is not of production quality, it is intended for
 research and educational purposes. The D Programming Language is a
 fairly complex language, and non-trivial features such as TLS and
 closures make it an interesting case study for generating IL code.
 
 Why do people never read the big red label saying Warning: not ready
 for use!?


Given the productivity increase that I could get, it's worth a shot.


 
 As for VS integration, so far as I know, there isn't any.  I'm also
 fairly certain that you can't combine different languages in a single
 project period.

Solutions are collections of projects. Each project can be in a different 
language. 


Re: D compiler for .NET

2009-06-10 Thread Kagamin
Jason House Wrote:

 Beyond compilation of the compiler, I found zero instructions on what to do 
 next.
I believe it's a traditional CUI compiler. Compile the compiler, open command 
prompt and run the compiler with source files. I think, it will say if 
something is wrong.

 How do I integrate the compiler into the .NET framework/visual 
 studio?
I think, the same way, as you would integrate any other .net language. See 
wikipedia for a list of them.

 I'd like to be able to add D files to existing solutions (with C# 
 code).
I don't think this feature is available, the author was focused on making CUI 
compiler only. If VS allows integration of 3rd party compilers, you can use 
that.
BTW how do you plan to get support for D syntax highlighting and intellisense?


Re: D compiler for .NET

2009-06-10 Thread Jason House
Kagamin Wrote:

 Jason House Wrote: 
  I'd like to be able to add D files to existing solutions (with C# 
  code).
 I don't think this feature is available, the author was focused on making CUI 
 compiler only. If VS allows integration of 3rd party compilers, you can use 
 that.
 BTW how do you plan to get support for D syntax highlighting and intellisense?

I don't. While really cool, such features are not essential. What I'm really 
hoping to get out of this is proper generic programming and enhanced 
compile-time validation. Manual copying of boiler plate code with small tweaks 
is sickening.



Re: D compiler for .NET

2009-06-10 Thread Kagamin
Jason House Wrote:

What I'm really hoping to get out of this is proper generic programming and 
enhanced compile-time validation.
 
I think these are done by frontend and frontend was kept intact. He didn't even 
wanted to add .net-specific pragmas to the frontend.


D compiler for .NET

2009-06-09 Thread Jason House
Earlier today, I tried to use the D compiler for .NET from 
http://dnet.codeplex.com/

Beyond compilation of the compiler, I found zero instructions on what to do 
next.  How do I integrate the compiler into the .NET framework/visual 
studio?  I'd like to be able to add D files to existing solutions (with C# 
code).  If I can do that, I'll probably push for some small adoption of D at 
work.  (I'm hoping mixins and templates will inspire the initial use of D)

Any tips or documentation on how to get started would be appreciated.



Re: D compiler for .NET

2009-06-09 Thread Daniel Keep


Jason House wrote:
 Earlier today, I tried to use the D compiler for .NET from 
 http://dnet.codeplex.com/
 
 Beyond compilation of the compiler, I found zero instructions on what to do 
 next.  How do I integrate the compiler into the .NET framework/visual 
 studio?  I'd like to be able to add D files to existing solutions (with C# 
 code).  If I can do that, I'll probably push for some small adoption of D at 
 work.  (I'm hoping mixins and templates will inspire the initial use of D)
 
 Any tips or documentation on how to get started would be appreciated.
 

The back-end code is not of production quality, it is intended for
research and educational purposes. The D Programming Language is a
fairly complex language, and non-trivial features such as TLS and
closures make it an interesting case study for generating IL code.

Why do people never read the big red label saying Warning: not ready
for use!?

As for VS integration, so far as I know, there isn't any.  I'm also
fairly certain that you can't combine different languages in a single
project period.