Dear Mike, It's up to you how to order your data. When you mention a data label in "at" clause of a field, ILASM expects you to eventually declare this label in a ".data" or ".data tls" statement. The references to data labels are resolved after the full source file (or set of source files) has been parsed. Thus, there is no specific requirement of ordering the data declarations and referencing them. The only limitation here is that if you reference a data label, it must be declared somewhere in your source.
Thanks, Serge -----Original Message----- From: James Michael DuPont [mailto:[EMAIL PROTECTED]] Sent: Sunday, February 16, 2003 2:09 AM To: [EMAIL PROTECTED] Subject: [DOTNET-ROTOR] Problem with ildasm and the "At" datasection Dear All, I have been experimenting with Rotor ILdasm and have noticed a possible bug or non-specified behaviour. .field assembly static valuetype '<PrivateImplementationDetails>'/'$$struct0x6000142-1' '$$method0x6000142-1' at D_0x00024000 This references a data array D_0x00024000 that has not been declared yet. I dont see anything in the spec that says about the ordering or dependancies in the file. please advice : mike ------------------------------------------------- .class private auto ansi '<PrivateImplementationDetails>' extends ['mscorlib']'System'.'Object' { .class nested private explicit sealed ansi '$$struct0x6000142-1' extends ['mscorlib']'System'.'ValueType' { .pack 1 .size 1024 } .field assembly static valuetype '<PrivateImplementationDetails>'/'$$struct0x6000142-1' '$$method0x6000142-1' at D_0x00024000 } .data D_0x00024000 = bytearray (00 00 00 00 96 30 07 77 2C 61 0E EE BA 51 09 99 37 BE 0B B4 A1 8E 0C C3 1B DF 05 5A 8D EF 02 2D) ===== James Michael DuPont http://introspector.sourceforge.net/ __________________________________________________________________ Gesendet von Yahoo! Mail - http://mail.yahoo.de Bis zu 100 MB Speicher bei http://premiummail.yahoo.de
