Re: [Ikvm-developers] Just looking for an advice about IKVM.Reflection.Emit

[Jeroen F. <je...@su...>]

Hi Luis,

This is exactly the scenario that IKVM.Reflection was built for. The IKVM static compiler (ikvmc) also used System.Reflection and I ran into several limitations that drove me to write IKVM.Reflection, also because the IKVM runtime (which shared a lot of code with ikvmc) still needed to be able to use System.Reflection, so it is easy to switch between the two with conditional compilation.

Since you specifically mention debugging info, I have to warn that IKVM.Reflection still uses the Microsoft symbol writer (because nobody so far has been unable to fully reverse engineer the .pdb file format), so any limitations therein are still present.

Regards,
Jeroen

> -----Original Message-----
> From: Luis Ochoa [mailto:ziu...@gm...]
> Sent: Friday, March 25, 2011 12:32 AM
> To: ikv...@li...
> Subject: [Ikvm-developers] Just looking for an advice about
> IKVM.Reflection.Emit
> 
> Hi I just read some very interesting articles about your Reflection.Emit
> implementation called IKVM.Reflection.Emit (like
> http://weblog.ikvm.net/CommentView.aspx?guid=9b7ada92-88d7-45c7-be83-
> 8e6f4f3ccb1b ), and my question is:
> 
> I wrote a Domain Specific Language for .Net using reflection emit  and
> saving the assembly with debug info (MarkSequencePoint), and I just
> found some issues with reflection, and after read articles about ikvm
> implementation of reflection.emit, I want to know if the IKVM
> implementation would be able to work as a substitute of M$ reflection at
> my code generator (I just create assemblies with debug info) ?, I'll
> able to save my assembly as I do with M$ implementation?
> 
> Regards, Luis.
>