Re[2]: [RFA] pei386 dll: auto-import patch

[Paul Sokolovsky <Paul dot Sokolovsky at technologist dot com>]

Hello Charles,

Charles Wilson wrote on Sunday, August 05, 2001:

[]
CW> I *believe* Ralf and Robert Collins were in contact. "My" version, was
CW> based on *Robert's* version, which he got from Ralf, who was up-to-date
CW> with your most recent version.  So, I *think* that what was finally
CW> committed WAS in fact, up-to-date with your stuff.  Except...

    Well, I confirm that that latest piece of patch (fixing segfault)
is in the cvs, and I have no changes relevant to features in question
in my local copy.

[]

CW> The "auto-import" feature won't work in those cases, naturally.
CW> However, the ld WILL successfully link "old-style" code with "old-style"
CW> implibs or with dll directly (functional interface only, just as
CW> before).  IOW, the new ld is drop-in replacement for old ld, given same
CW> sourcecode/object files/dlls/implibs.

    Absolutely right, my comments are concerned with new features, the
"old" operation is of course stayed the same.

[]

CW> Yes, but: in practice you are more likely to USE auto-export (e.g.
CW> --export-all) now that auto-import works.  Soooo...they are tied
CW> together, somewhat.  For instance, now you don't have to worry too much
CW> about creating a .def file and/or decorating exports when you want a dll
CW> of some library -- principle of least effort sez that newly ported libs
CW> (dlls) will NOT "do it the hard way"; --export-all (implicit?) will see
CW> much more use in the future, IMO.

    That's how I saw it from the beginning, too. (And why I made
auto-import on by default - I understand this can't be done in
official version just from the start.)

[]

CW> --Chuck




--
Paul Sokolovsky, IT Specialist
http://www.brainbench.com/transcript.jsp?pid=11135