[Issue 19502] windows command line arguments wrongly split
https://issues.dlang.org/show_bug.cgi?id=19502
him...@outlook.com changed:
What|Removed |Added
CC||him...@outlook.com
--- Comment #4 from him...@outlook.com ---
(In reply to Rainer Schuetze from comment #2)
> I don't see any difference in arguments for D or C++ (VC16). Both produce
> `C:\test"\blah.exe` for the example in the bug report.
>
> What OS/VC version are you seeing the difference with?
I'm on Windows 10 x64 with VC 2019. In a test with the following codes:
int main(string[] argv)
{
foreach(i; argv)
writeln(i);
return 0;
}
The cmd.exe raw displays:
C:\Users\XXX>"C:\Users\XXX\source\repos\test\x64\Debug\"\test.exe
C:\Users\XXX\source\repos\test\x64\Debug\
\test.exe
I reproduced this issue.
--
[Issue 19502] windows command line arguments wrongly split
https://issues.dlang.org/show_bug.cgi?id=19502 --- Comment #3 from Dlang Bot --- @LimiQS created dlang/druntime pull request #2932 "Fix Issue 19502: Implement correct split behavior" fixing this issue: - Fix Issue 19502: Implement correct split behavior https://github.com/dlang/druntime/pull/2932 --
[Issue 19502] windows command line arguments wrongly split
https://issues.dlang.org/show_bug.cgi?id=19502 Rainer Schuetze changed: What|Removed |Added CC||r.sagita...@gmx.de --- Comment #2 from Rainer Schuetze --- I don't see any difference in arguments for D or C++ (VC16). Both produce `C:\test"\blah.exe` for the example in the bug report. What OS/VC version are you seeing the difference with? --
[Issue 19502] windows command line arguments wrongly split
https://issues.dlang.org/show_bug.cgi?id=19502 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #1 from Dlang Bot --- @LimiQS created dlang/druntime pull request #2931 "Fix Issue 19502: Implement correct split behavior" fixing this issue: - Fix Issue 19502 - Implement correct split https://github.com/dlang/druntime/pull/2931 --
[Issue 16658] Win32API: default IE ver. set to 4.0 is too old
https://issues.dlang.org/show_bug.cgi?id=16658 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #2 from Dlang Bot --- @LimiQS created dlang/druntime pull request #2929 "Fix Issue 16658: Default IE version set to 6.0" fixing this issue: - Fix Issue 16658: Default IE version set to 6.0 IE 4 it too old. As it only supports up to WinNT 4.0, it's not available on WinXP or even Win2k. This leads to a mismatch with the default `_WIN32_WINNT = 0x500` (WinXP) value. Make the default IE version set to 6.0 could make more APIs available at default. Also, DMD now supports only `Windows 7 or later, 32 or 64 bit` and Windows 7 has reached End Of Life on 14 January 2020, it could reasonably set default value to: `_WIN32_WINNT = 0x601` and `_WIN32_IE = 0x800`. But this topic should be discussed in another PR. https://github.com/dlang/druntime/pull/2929 --
[Issue 18791] No VERSION file in DMD .zip distribution
https://issues.dlang.org/show_bug.cgi?id=18791 --- Comment #2 from Vladimir Panteleev --- 2.090 contains a VERSION file. However, now `make -f posix.mak` it fails with: dmd/doc.d(366): Error: file `"default_ddoc_theme.ddoc"` cannot be found or not in a path specified with `-J` make: *** [posix.mak:110: dmd] Error 1 Indeed, the file is nowhere to be found in the distribution. --
[Issue 15322] version(Unicode) should affect only default aliases
https://issues.dlang.org/show_bug.cgi?id=15322 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #1 from Dlang Bot --- @LimiQS created dlang/druntime pull request #2928 "Fix Issue 15322 - Correct versioning PENUM_PAGE_FILE_CALLBACK" fixing this issue: - Fix Issue 15322 - Correct versioning PENUM_PAGE_FILE_CALLBACK According to [Microsoft Docs](https://docs.microsoft.com/en-us/windows/win32/api/psapi/nf-psapi-enumpagefilesw), `EnumPageFilesW` always taking a `PENUM_PAGE_FILE_CALLBACKW` parameter. While before the correction, when version `Unicode` is not defined, `EnumPageFilesW` will be declared to take a `PENUM_PAGE_FILE_CALLBACKW`. https://github.com/dlang/druntime/pull/2928 --
[Issue 20559] Reference type + alias this + AA + AA.clear causes SEGV
https://issues.dlang.org/show_bug.cgi?id=20559 Dlang Bot changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #2 from Dlang Bot --- dlang/druntime pull request #2927 "Fix issue 20559: AA.clear segfault when used with alias this" was merged into stable: - 261124ff0aeb6ac577421045e7fa99f261796316 by Geod24: Fix issue 20559: AA.clear segfault when used with alias this https://github.com/dlang/druntime/pull/2927 --
[Issue 20559] Reference type + alias this + AA + AA.clear causes SEGV
https://issues.dlang.org/show_bug.cgi?id=20559 Dlang Bot changed: What|Removed |Added Keywords||pull --- Comment #1 from Dlang Bot --- @Geod24 created dlang/druntime pull request #2927 "Fix issue 20559: AA.clear segfault when used with alias this" fixing this issue: - Fix issue 20559: AA.clear segfault when used with alias this https://github.com/dlang/druntime/pull/2927 --
[Issue 20559] New: Reference type + alias this + AA + AA.clear causes SEGV
https://issues.dlang.org/show_bug.cgi?id=20559
Issue ID: 20559
Summary: Reference type + alias this + AA + AA.clear causes
SEGV
Product: D
Version: D2
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P1
Component: dmd
Assignee: nob...@puremagic.com
Reporter: pro.mathias.l...@gmail.com
Test code:
```
import std.stdio;
class Bar
{
int[string] aa;
alias aa this;
}
void main ()
{
scope b = new Bar;
b["Hello"] = 42;
b.clear; // SEGV happens here, next line is never reached
writeln("Oopsie");
}
```
This happens because 'clear' is defined as:
> void clear(T : Value[Key], Value, Key)(T aa)
And the code just blindly casts T to a `struct AA`:
https://github.com/dlang/druntime/blob/1049bb806679436103f8174c1f77541d5ad99091/src/object.d#L2167-L2170
--
[Issue 20548] Use bit vector instead of bool[] in RandomCover when choices cannot be packed in a single word
https://issues.dlang.org/show_bug.cgi?id=20548 --- Comment #3 from Dlang Bot --- dlang/phobos pull request #7390 "Issue 20548 followup: in 32-bit builds RandomCoverChoices allocates more memory than needed for the bit vector" was merged into master: - 67e4a0868472945818e9a417ea3c0ca4645b5fab by Nathan Sashihara: Issue 20548 followup: in 32-bit builds RandomCoverChoices allocates more memory than needed for the bit vector https://github.com/dlang/phobos/pull/7390 --
[Issue 12931] Make const, immutable, inout, and shared illegal as function attributes on the left-hand side of a function
https://issues.dlang.org/show_bug.cgi?id=12931 --- Comment #21 from Dlang Bot --- dlang/phobos pull request #7389 "[Trivial] Issue 12931: Move shared to the RHS" was merged into master: - 3140fb9e3aa2b6b6eabc1ce718cc88f8830d36d5 by Geod24: Issue 12931: Move shared to the RHS https://github.com/dlang/phobos/pull/7389 --
[Issue 20551] In @safe code and using delegates, it's possible to escape references to function frame
https://issues.dlang.org/show_bug.cgi?id=20551 --- Comment #8 from Basile-z --- Thanks for your time Razvan. --
[Issue 12931] Make const, immutable, inout, and shared illegal as function attributes on the left-hand side of a function
https://issues.dlang.org/show_bug.cgi?id=12931 --- Comment #20 from Dlang Bot --- @Geod24 created dlang/dmd pull request #10757 "Fix issue 12931: Make ambiguous qualifiers illegal on the LHS of a function" fixing this issue: - Fix issue 12931: Make ambiguous qualifiers illegal on the LHS of a function This has been a pain point for many D users for years, both new and old, as can be seen from the discussions on the issue. It is however a potentially disruptive deprecation. Note: The test for issue 5962 in test/runnable/xtest46.d has been removed as the issue was only present with prefix syntax. https://github.com/dlang/dmd/pull/10757 --
[Issue 12931] Make const, immutable, inout, and shared illegal as function attributes on the left-hand side of a function
https://issues.dlang.org/show_bug.cgi?id=12931 --- Comment #19 from Dlang Bot --- @Geod24 created dlang/phobos pull request #7389 "[Trivial] Issue 12931: Move shared to the RHS" mentioning this issue: - Issue 12931: Move shared to the RHS https://github.com/dlang/phobos/pull/7389 --
[Issue 20558] New: __DATE__ and __TIMESTAMP__ use US-centric formats
https://issues.dlang.org/show_bug.cgi?id=20558 Issue ID: 20558 Summary: __DATE__ and __TIMESTAMP__ use US-centric formats Product: D Version: D2 Hardware: x86_64 OS: Linux Status: NEW Severity: enhancement Priority: P1 Component: dmd Assignee: nob...@puremagic.com Reporter: m...@qtrac.eu I suggest adding __ISODATE__ and __ISOTIMESTAMP__ which should both use ISO8601 date formats. See https://github.com/dlang/dlang.org/pull/2747#issuecomment-581239122 --
