[Mono-bugs] [Bug 31984][Maj] Changed - mcs doesn't correctly resolve const value uses depending on file compilation order

[bugzilla-daemon@rocky.ximian.com]

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 miguel@ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=31984

--- shadow/31984	Wed Oct  9 02:11:10 2002
+++ shadow/31984.tmp.12962	Thu Oct 10 01:12:31 2002
@@ -1,14 +1,14 @@
 Bug#: 31984
 Product: Mono/MCS
 Version: unspecified
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Major
 Component: Misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: vladimir@pobox.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -46,6 +46,16 @@
 compild with "mcs -o t9 t9b.cs t9a.cs" (note switched order of files), I get:
 
 t9b.cs(5) error CS0117: `T.X.Z' does not contain a definition for `BLAH_LIB'
 
 csc behaves as expected.  Blocking future commit of gtk#-for-win32 patch,
 as it can't compile under linux without a hack :)
+
+------- Additional Comments From miguel@ximian.com  2002-10-10 01:12 -------
+I think that a quick hack would be to get constants defined before
+attributes are emitted (currently attributes are processed before
+everything else).
+
+But I am starting to believe that this is the wrong approach.  I might
+want to go a different path which is to have every type trigger
+recursive definitions.  The changes are rather significant, so I want
+to think about this for a while.