On Thursday, 21 October 2021 at 23:06:18 UTC, jfondren wrote:
On Thursday, 21 October 2021 at 22:23:50 UTC, data pulverizer
wrote:
I'd first check that the type names look OK in the processed C.
If they do, then it's an importc bug. Those are still getting
reported, but yours might be new.
On Friday, 22 October 2021 at 05:54:21 UTC, Kirill wrote:
I am not a compiler expert, but I genuinely would like to know
why we have Dmain.
I've been looking at the generated assembly code recently and
noticed the _Dmain function. I didn't notice it before. Then
there is main, where Dmain is
On Friday, 22 October 2021 at 07:00:25 UTC, Mike Parker wrote:
The entry point for your program is a function `_start`. That's
implemented in the C runtime, which all D programs depend on.
It in turn calls `main`, as it does for C and C++ programs.
It is possible, in both C and D, to write
Actually C runtime is many megabytes in size.
On Friday, 22 October 2021 at 07:00:25 UTC, Mike Parker wrote:
[...]
Thank you for such a clear explanation Mike and for a quick reply!
On Friday, 22 October 2021 at 06:11:35 UTC, data pulverizer wrote:
On Thursday, 21 October 2021 at 23:06:18 UTC, jfondren wrote:
[...]
I've double-checked and the types names are fine in translated
C file.
[...]
I think you ran into this
Hi, all!
I use the hunt-entity library to work with MySQL. I get the
hunt.Exceptions.TimeoutException: "Timeout in 30 secs" when
trying to connect. I configured MySQL and ran the code from the
instructions https://github.com/huntlabs/hunt-entity
MySQL:
mysql Ver 8.0.27 for Linux on x86_64
On Friday, 22 October 2021 at 11:42:34 UTC, greenbyte wrote:
Hi, all!
I use the hunt-entity library to work with MySQL. I get the
hunt.Exceptions.TimeoutException: "Timeout in 30 secs" when
trying to connect. I configured MySQL and ran the code from the
instructions
I have a simple vibe-d project built with dub. Running the
command, dub build --force returns the following output:
Performing "debug" build using
E:\Programs\D\dmd2\windows\bin\dmd.exe for x86_64.
mir-linux-kernel 1.0.1: building configuration "library"...
taggedalgebraic 0.11.22: building
On Friday, 22 October 2021 at 19:56:37 UTC, Ruby The Roobster
wrote:
I have a simple vibe-d project built with dub. Running the
command, dub build --force returns the following output:
I'd start by running `dub -v build --force` instead, to see the
exact commands that dub is running.
On 10/22/21 5:21 PM, jfondren wrote:
On Friday, 22 October 2021 at 19:56:37 UTC, Ruby The Roobster wrote:
I have a simple vibe-d project built with dub. Running the command,
dub build --force returns the following output:
I'd start by running `dub -v build --force` instead, to see the exact
On Friday, 22 October 2021 at 21:21:41 UTC, jfondren wrote:
On Friday, 22 October 2021 at 19:56:37 UTC, Ruby The Roobster
wrote:
I have a simple vibe-d project built with dub. Running the
command, dub build --force returns the following output:
I'd start by running `dub -v build --force`
On Friday, 22 October 2021 at 21:57:02 UTC, Ruby The Roobster
wrote:
On Friday, 22 October 2021 at 21:21:41 UTC, jfondren wrote:
On Friday, 22 October 2021 at 19:56:37 UTC, Ruby The Roobster
wrote:
I have a simple vibe-d project built with dub. Running the
command, dub build --force returns
On Friday, 22 October 2021 at 09:01:53 UTC, Kagamin wrote:
Actually C runtime is many megabytes in size.
A couple of samples:
$ wc -c /usr/lib/libc-2.33.so
2150424 /usr/lib/libc-2.33.so
% wc -c /lib/libc.so.7
1981952 /lib/libc.so.7
I would hardly call two megabytes 'many'.
14 matches
Mail list logo