Is it possible to import module that is not in the module's
current directory's folder or subfolders?
For example:
I want to import `somemodule2.d` and `somemodule3.d` into a
**`somemodule.d`**
**.\somefolder\somemodule.d**
.\somemodule2.d
.\someotherfolder\somemodule3.d
On Saturday, 2 July 2022 at 21:36:50 UTC, mw wrote:
Actually, can you create a github repo, I'm sure people will
send you a working PR.
Yes I can. I will inform here once I did it.
On Thursday, 23 June 2022 at 16:16:26 UTC, vc wrote:
I've try this '\0'*10 and didn't work, i want the results be
\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
```d
string nulls = '\0'.repeat(10).array;
```
— Bastiaan.
On Saturday, 2 July 2022 at 20:43:41 UTC, Vinod KC wrote:
On Saturday, 2 July 2022 at 14:32:11 UTC, apz28 wrote:
dmd -of=dimedll.dll dimedll.d dimedll.def
dmd dime.d dimedll.di
Thanks for the reply. Well, I am sorry to say that your
suggestions resulted in failure.
First of all, when I used
On Saturday, 2 July 2022 at 14:32:11 UTC, apz28 wrote:
dmd -of=dimedll.dll dimedll.d dimedll.def
dmd dime.d dimedll.di
Thanks for the reply. Well, I am sorry to say that your
suggestions resulted in failure.
First of all, when I used this command -- ` dmd -of=dimedll.dll
dimedll.d
On Saturday, 2 July 2022 at 09:42:17 UTC, Loara wrote:
But you first said "The compiler should deduce if a `scope`
pointer points to heap allocated data or not" and when someone
tells you this should happen only for not `scope` pointers you
say "But the compiler doesn't do that".
This
Below is working on Windows
--file dimedll.d:
module dimedll;
import core.sys.windows.windows;
import core.sys.windows.dll;
import std.stdio;
mixin SimpleDllMain;
export void testFunc()
{
writeln("This is from dll");
}
--file dime.d:
import core.sys.windows.windows;
With LDC, this is sufficient for this trivial example:
```d
module dimedll;
export void testFunc() { // export only needed when compiling
with `-fvisibility=hidden`
import std.stdio;
writeln("This is from dll");
}
```
`ldc2 -shared dimedll.d` generates import lib + DLL.
```d
import
On Saturday, 2 July 2022 at 01:05:25 UTC, Ali Çehreli wrote:
3) The users of this dll should import that .di file (declaring
the functions themselves won't work):
Ali
Hi, Thanks for the reply. I have tried your suggestion. First, I
compiled my dll's source code with `-H` switch as you
On Thursday, 30 June 2022 at 21:30:39 UTC, Ola Fosheim Grøstad
wrote:
I don't understand what you mean, it could, but it doesn't. And
if it did then you would not need `scope`…
If the compiler doesn't optimize your code is a compiler issue.
When you use the `scope` attribute you're [forcing
10 matches
Mail list logo
