On Sunday, 4 September 2022 at 03:50:56 UTC, Ali Çehreli wrote:
For example, there is fixedsizearray, which does not belong to
any package:
Yeah, this is bad design since two separate people might reuse
the name and then end users - even if it comes through a couple
layers of dependencies
I've been reading up fairly recently on RPATH for *nix which does what
you want. Unfortunately as far as I've found there is no way to do this
on Windows without an extra executable.
On 9/4/22 09:35, Paul Backus wrote:
// TODO: omit stack trace only if assert was thrown
// directly by the unittest.
Thank you but I mean... :) I can understand removing a backtrace from
the eyes of an end user but the consumer of a unittest output is a
developer, no?
Ali
On Sunday, 4 September 2022 at 01:52:11 UTC, Ali Çehreli wrote:
Should the package be the author's name: acehreli.a,
acehreli.b, and acehreli.c?
This is what I'd suggest. You want something that nobody else is
likely to step on throughout the entirety of the D ecosystem. It
doesn't have to
The program output is different whether an Error is thrown from main or
from the unittest block:
void foo(string s)
in (s != "hello") {
}
unittest {
foo("hello"); // No stack backtrace
}
void main() {
foo("hello"); // Yes stack backtrace
}
Ali
**Folder structure**
.\msvcr120.dll
.\folder1\HelloWorld.exe
.\folder2\HelloWorld.exe
Basic binaries produced by DMD.exe compiler require
Microsoft Compiler Runtime DLL
As you might know that a basic D Language example
`HelloWorld.exe`
On Sunday, 4 September 2022 at 17:43:01 UTC, IchorDev wrote:
I'm trying to implement a custom exception system in BetterC.
Does anyone know how I'd go about getting a stack trace so that
I can print it to stdout? :)
I was thinking of utilising UDAs & `__LINE__` but it turns out
that UDAs don't
On Sunday, 4 September 2022 at 14:14:55 UTC, Ali Çehreli wrote:
The program output is different whether an Error is thrown from
main or from the unittest block:
Because the default test runner catches the Error, and doesn't
print the stack trace:
I'm trying to implement a custom exception system in BetterC.
Does anyone know how I'd go about getting a stack trace so that I
can print it to stdout? :)
I was thinking of utilising UDAs & `__LINE__` but it turns out
that UDAs don't let you inject code, which is a shame!
On Sunday, 4 September 2022 at 08:17:13 UTC, Nick Treleaven wrote:
You may be able to use dustmite to automatically reduce the
code to a minimal test case:
https://dlang.org/blog/2020/04/13/dustmite-the-general-purpose-data-reduction-tool/
Send my regards to the planet smasher.
What do I
On Saturday, 3 September 2022 at 21:20:01 UTC, solidstate1991
wrote:
During unittest in my own fork of std.experimental.xml (link:
https://github.com/ZILtoid1991/experimental.xml ), potentially
an error so severe is present, that it causes to crash the
compiler (both DMD and LDC2, on Windows).
I tried to compile on the Raspberry Pi 400, now I'm getting
segmentation fault during compilation with LDC. Still no idea
what causes it, nor how to reduce it. Moved the codebase to a new
repository, gave it a proper DOMString implementation instead of
using it as a template name, and I'm
On Sunday, 4 September 2022 at 15:16:47 UTC, BoQsc wrote:
**Folder structure**
.\msvcr120.dll
.\folder1\HelloWorld.exe
.\folder2\HelloWorld.exe
You don't need to do this. msvcr120.dll is already shipped with
the DMD compiler at
[DMD-install-folder]\windows\bin64\msvcr120.dll. (It is also
I wrote out this tutorial for bitshifting in D and it's probably
not the best but it gets the general idea across for new users on
how to have multiple values reside in one memory address.
Here is the link to the tutorial
On Saturday, 3 September 2022 at 14:37:16 UTC, Steven
Schveighoffer wrote:
On 9/2/22 3:15 PM, cc wrote:
Tried casting away shared as a workaround but I assume that
will cause some kind of TLS catastrophe.
I think it will be fine, but you may have an issue. You are
returning a non-shared
15 matches
Mail list logo
