[Mono-list] Silly question (for documentation)
zac at zacbowling.com
Mon Mar 6 18:29:22 EST 2006
>> I know that CSC creates a temp directory in where ever %TEMP% is
>> pointed to, to create the object files and deletes them when its all
>> done building but the compiler inlined in Visual Studio creates a local
>> directory to store the object files (the lovely 'obj' dir you find
>> lerking around).
> I doubt very much that CSC generates anything resembling an "object
> file". You are confused.
"Object file" was the wrong term to use. I was thinking of
incrimentally compiling some IL backends and storing it off in some
files somewhere so it could be brought back together in the end.
However, I've gone back and observed it and examined the files a bit
more closely, and it looks more like its just garbage for the debuggers
and designers more then anything. I did catch thoigh what I'm pretty
sure is just the PE header of the assembly it was generating before it
deleted it but a few bits are missing. Oh well.. not really all that
exciting or important.
>> Not sure how credible this is but it says on the DotGNU wiki about how
>> their compiler works compared to ours: "..CSCC is a 3 step compile,
>> assemble and link compiler, while MCS is a direct codegeneration in
>> memory with Reflection.Emit." They might be doing something completely
>> different system then anyone else out there
> They generate a text file with the il assembly, which later they pass on
> to an IL assembler to assemble. Thats all there is to it.
oh really?.. uhh.. wow... hmm... that's kind of interesting, but I
think I'm going to just leave that one alone then...
More information about the Mono-list