On Thursday, 28 April 2022 at 12:36:56 UTC, Dennis wrote:
On Thursday, 28 April 2022 at 12:10:44 UTC, bauss wrote:
On Wednesday, 27 April 2022 at 15:40:49 UTC, Adam D Ruppe
wrote:
but this got killed due to internal D politics. A pity.
A tale as old as time itself
In this case, it was actua
On Thursday, 28 April 2022 at 12:36:56 UTC, Dennis wrote:
In this case, it was actually a trailing whitespace in the
changelog entry making the test suite fail, but the PR author
Stefan's own `assert(__ctfe);` approach was better anyway...
On Thursday, 28 April 2022 at 12:10:44 UTC, bauss wrote:
On Wednesday, 27 April 2022 at 15:40:49 UTC, Adam D Ruppe wrote:
but this got killed due to internal D politics. A pity.
A tale as old as time itself
In this case, it was actually a trailing whitespace in the
changelog entry making th
On Wednesday, 27 April 2022 at 15:40:49 UTC, Adam D Ruppe wrote:
but this got killed due to internal D politics. A pity.
A tale as old as time itself
On Wednesday, 27 April 2022 at 14:21:15 UTC, Claude wrote:
The operation requiring the D-runtime is appending the array,
but it should **only** be done at compile-time.
In that case, you want to prove to the compiler it is only called
at compile time by encapsulating the function inside a temp
On Wednesday, 27 April 2022 at 14:34:27 UTC, rikki cattermole
wrote:
This works:
Cool, thanks.
Unfortunately, with that implementation, I need to know the
maximum size for the array. It works for that particular example,
but in the context of an XML file analysis, it's a bit awkward.
Regar
On Wednesday, 27 April 2022 at 14:27:43 UTC, Stanislav Blinov
wrote:
This is a long-standing pain point with BetterC (see
https://issues.dlang.org/show_bug.cgi?id=19268).
That's what I was afraid of... Thanks for the link to the
bug-report.
On Wednesday, 27 April 2022 at 14:27:43 UTC, Stanis
This works:
```d
struct Data
{
int[] digits;
}
int parseDigit(char c) pure
{
return c - '0';
}
Data parse(string str) pure
{
Data data;
if (__ctfe) {
size_t used;
data.digits.length = str.length;
while (str.length != 0)
{
// Skip spa
On Wednesday, 27 April 2022 at 14:21:15 UTC, Claude wrote:
This is a long-standing pain point with BetterC (see
https://issues.dlang.org/show_bug.cgi?id=19268).
As for this:
If I compile without the BetterC switch, compilation actually
works but I'll have some linker issues:
```
$ gcc test.
On Wednesday, 27 April 2022 at 14:21:15 UTC, Claude wrote:
data.digits ~= parseDigit(str[0]);
Dynamic arrays are not supported using -betterC
Andrea
Hello,
I want to make a SAX XML parser in D that I could both use at
run-time or compile-time.
Also when I use it at compile-time, I would like to use BetterC
so I don't have to link D-runtime.
But I have some compilation problems. I use GDC (GCC 9.4.0).
Here's a reduced sample code:
```
Le 16/03/2018 à 22:58, Xavier Bigand a écrit :
Le 15/03/2018 à 01:09, Flamaros a écrit :
On Wednesday, 14 March 2018 at 01:17:54 UTC, rikki cattermole wrote:
You will still need DllMain, that is a platform requirement.
I am not sure about that because when DllAnalyser don't see it in the
ope
Le 15/03/2018 à 01:09, Flamaros a écrit :
On Wednesday, 14 March 2018 at 01:17:54 UTC, rikki cattermole wrote:
You will still need DllMain, that is a platform requirement.
I am not sure about that because when DllAnalyser don't see it in the
opengl32.dll from the system32 directory. And the d
On Wednesday, 14 March 2018 at 01:17:54 UTC, rikki cattermole
wrote:
You will still need DllMain, that is a platform requirement.
I am not sure about that because when DllAnalyser don't see it in
the opengl32.dll from the system32 directory. And the
documentation indicate that it is optional.
You will still need DllMain, that is a platform requirement.
As I am trying to do a dll that acts exactly like one written in C, I am trying
to compile my code with the -betterC option. So I would not need the DllMain
function.
I am not sure that I use the best syntax for my CTFE function to be able to
make it works with the option -betterC and to maint
16 matches
Mail list logo
