🚀 go-pugleaf

I am porting a windows app written with MSC 6.0 and SDK 3.0 to BC++ 2.0
The C source codes compiled fine with minor changes to associate function
prototypes with each individual module vs putting all of them in one 
.h file and include it in all module files.

However, the linker gives warning about exporting dialog functions:

	Attempt to export non-public symbol XXXXX

where XXXXX is the name of the dialog function.  The dialogs are called
through MakeProcInstance(XXXXX, hInst) which are all listed under
EXPORTS in .def file.

I have tried the options All windows functions exportable and Explicit
export for BC++ 2.0  The linker still gives the same warning.

When I run the application in windows 3.0, some dialogs would come up
but don't function the way they are supposed to; other dialogs would
cause UAEs/system reboot.  This behaviour would indicate that the dialogs
are not properly exported and associated with the instance's data segment.

How would I export them properly under BC++ 2.0?

Thank you,


--
Jin Li                               (416) 978-6619  //  Gin & Tonic mix well
Dynamic Graphics Project, Dept. of Computer Science  \\
University of Toronto, Ontario, Canada   M5S 1A1     //
jinli@dgp.utoronto.ca          uunet!utai!dgp!jinli  \\    No bugs, no bucks