OpenEuphoria

Re: 32-bit Ints in Eu2C dlls

• Posted by "Juergen Luethje" <j.lue at gmx.de> Feb 05, 2005
• 451 views

Matt Lewis wrote:

> Juergen Luethje wrote:
>>
>> Not a problem at all.
>> Again you "did the impossible". Well, I probably shouldn't be surprised
>> by that any more.   Thanks a lot!!
>> I think I was able to "dot an i". I sent you the code privately.
>
> Got it.  Thanks.  It was something I had sort of thought about doing,
> but was too lazy to think too hard about it, since it didn't really do
> anything, but I think I probably will add it in.

Of course it's a minor issue. I just thought people who have a close
look at a DLL might wonder what those routines are doing, and why I
didn't document them. I'm currently working on the next version of a
DLL, that I distribute on my website, so your tool comes at the right
time for me. 

Yesterday I just used your small file 'test.ew' to test your program,
and then I had that idea, better not to export 'make_atom()' and
'make_atomu()'.
Today I built the current version of my DLL, using "make_atom". It
worked fine! After translating the code, I realized that the .def file
containd 114 routine names. But I only want 11 routines to be exported!
So it doesn't matter, whether or not there are 2 more names in the .def
file, it isn't "clean" anyway. Sorry, I didn't think of that yesterday.

So until I have a better idea I'll do the same as before, concerning the
.def file. For each project, I'll write the desired .def file by hand,
and after translation I'll replace the automatically produced .def file
with my hand-written .def file. The replacement can be done automatically
by a batch file.

The cause of this clutter is, that there is no way to tell the translator
explicitely, which routines I want to export, and that the translator
automatically exports *all* global routines -- even those, which are in
included files. Again that scope issue concerning "include" ... 

<snip>

Regards,
   Juergen