[Mono-dev] Compatible dll's
joe at otee.dk
Wed Oct 11 13:24:50 EDT 2006
>> What is actually going to happen if i would just load the new and changed
>> dll and it would actually have different signatures? Would it just crash? Or
>> give me a runtime exception at some point when jitting one of the functions?
>> Maybe i could make mono preload the dll completely and if that fails i know
>> they are not compatible?
> What happens depends on the change. A diffrent method signature is the
> same as a missing method and you should get a missing method exception.
> Other changes may result in different exceptions and you may well hit
> some crash, also depending if we have implemented checks etc.
> Maybe you should describe the problem you're trying to solve instead of
> asking if a weird solution would work.
I am trying to optimize compile time. Unity splits compilation into a couple
of different dll's, depending on which folder the scripts are in.
Compilation is started whenever a user saves a script. Once a dll has
finnished compiling, all dependent dll's need to be compiled.
I would like to avoid compiling the dependent dll's whenever it is possible.
Simply because short compile times make our customers happy.
So my idea was to detect if the signature of the dll we compiled against is
the same as the one we will now replace it with. If the signature is the
same i can simply skip compiling all dependent scripts, thus save a bunch of
unnecessary compile time.
More information about the Mono-devel-list