<br><br><div class="gmail_quote">On Sat, Feb 9, 2013 at 3:18 PM, Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com" target="_blank">siguctua@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi, Eliot<br>
<br>
i thought about it, and i don't like it.<br>
I am in favor of exporting stuff explicitly, rather than implicitly by<br>
compiler..<br>
because with implicit exports, you never know whether given symbol<br>
will be visible or not..<br>
and you have to guess and hope instead of being confident.<br>
<br>
It would be nice if we could have a way to export all functions and variables<br>
which has <api> pragma.. because exporting everything , first is not<br>
needed, second<br>
it will expose some symbols which are really private to VM which is<br>
not very good from design perspective.<br></blockquote><div><br></div><div>I agree. All you need to do on WIndows is to collect all the functions that are either marked as api, export: true or in requiredMethodNames and write a .def file. The syntax of the def file is easy enough (just a list of names IIRC) that a Makefile could munge it to produce a set of flags for a linker (but it's a *lot* of flags :) ). You might look at where the CodeGenerator produces cointerp.h and cogit.h and add the generation there.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I am not really know what and where can be changed to do that.. so,<br>
meanwhile i will use primitives.<br>
But for the future it would be really nice to have that.<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Best regards,<br>
Igor Stasenko.<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>