calling C code // drivers
Sat Sep 20 21:50:22 CEST 2003
I sat and daydreamed today, and I have a few questions that I hope someone
will be kind enough to answer...
Are there any specific reasons to use the current way of interfacing with C
code (i.e. the drivers) as it is today opposed to another one? What are the
arguments for not using a more direct way than today? What I have in mind is
the fact that with Hipe Erlang functions are compiled to native code - in
theory, I can't see any reason why one couldn't compile C code to look like
Hipe generated one. Thus we could have everybody write their own BIFs!! :-)
In any case, it would be easier to interfacce with external libraries (and
also the result might be a little faster?)
Is this possible at all, or am I unaware of issues that forbid it?
More information about the erlang-questions