■
 Здорово, andrew !

08 Hоя 02, andrew clarke тулит свою месагу к Tobias Ernst:

ac> OK, I take some of that back - I looked at some of the more recent
ac> bleeding-edge binaries of HPT & FidoConfig, and you're using DLLs for
ac> SMAPI & FidoConfig (although not for Msged yet).  I still think a lot
ac> of the calling-convention stuff could be simplified though, eg.
ac> doing:

ac> #define EXPENTRY WINAPI

ac> for the Win32 functions that are being exported.  That should allow
ac> the same DLLs to be used with different Windows compilers (where
ac> currently you seem to have compiler-specific DLLs, eg. presumably
ac> smapimvc.dll is for MSVC only).

You can define it for your compiler in smapi/compiler.h

ac> Also, I noticed with HPT 1.3.0 that the SMAPI & FidoConfig DLLs need
ac> to be in the same directory as HPT.EXE, otherwise it won't run.  Or I
ac> could put them in \WINNT\SYSTEM32\, but I don't like that idea much.
ac> So I think ideally HPT should be using getenv("FIDOCONFIG") then
ac> stripping the filename and replacing it with "BIN\SMAPI.DLL" or
ac> whatever, then using LoadLibrary().  This might end up being more work
ac> than it sounds though, but it's just an idea.  It may/may not be

It's bad idea. because it's very specific win32 style of coding. not
portable for other OS then win or OS/2.





 Покедова.                                                 [Team LSET]

--- Touch And Go - StraightTo Number One (Dreamca - mpg123/w32 0.59s-mh2