On Wednesday, 18 January 2017 at 04:25:42 UTC, Mike Parker wrote:
extern(C), not simply extern. It turns off the name mangling.
But really, the proper thing to do is to drop the prototype and
import the module with the implementation. It's tge way modules
are intended to be used. Unless
Thanks loads. I got it working using those modules.
~Sam
On Wednesday, 18 January 2017 at 23:12:15 UTC, Mike Parker wrote:
(source files), then use the import statement to make the
declarations in other modules.
Sorry, this should read "make the implementations available to
other modules".
On Wednesday, 18 January 2017 at 19:28:20 UTC, Samwise wrote:
On Wednesday, 18 January 2017 at 04:25:42 UTC, Mike Parker
wrote:
extern(C), not simply extern. It turns off the name mangling.
But really, the proper thing to do is to drop the prototype
and import the module with the
On Wednesday, 18 January 2017 at 04:25:42 UTC, Mike Parker wrote:
extern(C), not simply extern. It turns off the name mangling.
But really, the proper thing to do is to drop the prototype and
import the module with the implementation. It's tge way modules
are intended to be used. Unless
On Wednesday, 18 January 2017 at 04:06:23 UTC, Samwise wrote:
On Wednesday, 18 January 2017 at 03:51:50 UTC, ketmar wrote:
On Wednesday, 18 January 2017 at 03:37:46 UTC, Samwise wrote:
extern int getReturnCode() {
return 4;
}
still does not compile using the command from above. I may
On Wednesday, 18 January 2017 at 04:06:23 UTC, Samwise wrote:
I have both the header in hello.d and the actual function in
getReturnCode.d as extern, and it still fails with the same
error.
nope. it works.
On Wednesday, 18 January 2017 at 03:51:50 UTC, ketmar wrote:
On Wednesday, 18 January 2017 at 03:37:46 UTC, Samwise wrote:
extern int getReturnCode() {
return 4;
}
still does not compile using the command from above. I may
very well be misunderstanding you though.
yep. *both*
On Wednesday, 18 January 2017 at 03:37:46 UTC, Samwise wrote:
extern int getReturnCode() {
return 4;
}
still does not compile using the command from above. I may very
well be misunderstanding you though.
yep. *both* prototype and real declaration should be `extern(C)`.
`(C)` part is
On Wednesday, 18 January 2017 at 03:25:47 UTC, Stefan Koch wrote:
On Wednesday, 18 January 2017 at 03:11:08 UTC, Samwise wrote:
On Wednesday, 18 January 2017 at 02:48:45 UTC, James Buren
wrote:
Import the source file containing the external function
instead of writing that prototype. It should
On Wednesday, 18 January 2017 at 03:11:08 UTC, Samwise wrote:
On Wednesday, 18 January 2017 at 02:48:45 UTC, James Buren
wrote:
Import the source file containing the external function
instead of writing that prototype. It should compile then.
This seems like a workaround more than a permanent
On Wednesday, 18 January 2017 at 02:48:45 UTC, James Buren wrote:
Import the source file containing the external function instead
of writing that prototype. It should compile then.
This seems like a workaround more than a permanent solution. It
would work, but still. I'm also not sure about
Import the source file containing the external function instead
of writing that prototype. It should compile then.
Alright. For the sake of this argument, I'm going to post all the
stuff about a really tiny boring program that quite literally
does nothing, even though I found this issue when I was working
with a much larger project with more functions. Basically I'm
getting errors when I attempt to compile
14 matches
Mail list logo
