Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by lupus at ximian.com.http://bugzilla.ximian.com/show_bug.cgi?id=75881
--- shadow/75881 2005-08-23 15:47:56.000000000 -0400
+++ shadow/75881.tmp.15381 2005-08-24 10:08:24.000000000 -0400
@@ -46,6 +46,25 @@
Proposed patch
------- Additional Comments From miguel at ximian.com 2005-08-23 15:47 -------
Paolo, this is necessary for our mainsoft collaboration, could you
review/approve?
+
+------- Additional Comments From lupus at ximian.com 2005-08-24 10:08 -------
+Ankit, please commit, thanks.
+Could you test also if ilasm allows to encode a scope typeref
+where the name is itself a nested type expression?
+That is, say you have a class like:
+class T {
+ class A {
+ class B {
+ }
+ }
+}
+
+And see if it's possible to output a scope name of:
+ "A/B"
+You may need to change ilasm or PEAPI to do this and check if the
+resulting assembly ius understood by peverify and the MS runtime.
+In that case we want to use something like the return_nested_in()
+function (and making the runtime lazily load the nested types).