@empty
" Each TPC DLL would have to export a list of the DLLs it requires, though."
Yeah, I was thinking of that as I posted. Wouldn't you have to make the DLLs as delay import as well? I mean, there is a field somewhere in the file format for them that specifies that. It was either in the Optional Header(probable) or PE Header(Improbable, but still possible. I forget). Otherwise loading them in would just cause Windows to go searching for their dependicies defeating their whole purpose. Or not?
I haven't really looked into the whole delay import thing that closely. I saw some fields in the PE file format for them, but I read that it had to be handled manually and that there was some DLL that came with VC++ that did it or something like that. So I lost interest and moved on to something more relevant.
Does windows enforce the loading of other dependent DLLs when you load them in manually? If they do then I'm sure Lee would have to change the current DLLs so they were all tagged as delay-import. Not too big of a deal of though.
"The method is widely spread actually (Blitz does it the same way)."
Yeah, I know. You told me once.
"Interestingly MS's .Net JIT compiler had the same problem with the first versions of Windows XP SP2. According to MS it's a problem of wrongly tagged allocated memory."
Interesting. I hadn't heard about that.
"Or wait for .NET's break-through. I'm not a big fan of it, but I'm sure it will succeed."
Yes, but I guy can dream can't he?
*dreams of a .LIB future of real small executables*
@Raven
"the more i look and hear what each person who has delt with dbp has to say; just looks more and more that this is mearly a scriptable engine and not an actual language."
What about it makes you think that? Clunky file sizes? VB had that once but it was still considered a language.
I don't get where you are coming from here.