Custom calling conventions
Alex Rønne Petersen
xtzgzorex at gmail.com
Tue Feb 21 11:57:01 PST 2012
On 21-02-2012 20:43, Manu wrote:
> On 21 February 2012 19:10, Alex Rønne Petersen <xtzgzorex at gmail.com
> <mailto:xtzgzorex at gmail.com>> wrote:
> On 21-02-2012 18:03, Manu wrote:
> On 21 February 2012 16:59, Michel Fortin
> <michel.fortin at michelf.com <mailto:michel.fortin at michelf.com>
> <mailto:michel.fortin at michelf.__com
> <mailto:michel.fortin at michelf.com>>> wrote:
> On 2012-02-21 11:03:09 +0000, Manu <turkeyman at gmail.com
> <mailto:turkeyman at gmail.com>
> <mailto:turkeyman at gmail.com <mailto:turkeyman at gmail.com>>> said:
> Interesting point.
> Java (or any VM based language) can't hard link to the binary, so it
> never could try and call back in through an extern-ed function
> Sure it could. Why wouldn't it be able to? This is how extern +
> DllImport works in C#.
> But that only works because C# has DLL support, which knows about the C
> calling convention, so you just need to export an extern(C) in that
> case, like any regular DLL.
Surely Java 'native' methods require the native functions to conform to
some calling convention?
More information about the Digitalmars-d