On Tuesday, 18 July 2023 at 07:19:44 UTC, Vladimir Panteleev
wrote:
Seeing this link failure on Windows:
https://github.com/CyberShadow/ae/actions/runs/5574489393/jobs/10184021009#step:8:30
Looks like an MS link SNAFU.
lld-link also fails, so this looks like a DMDBE bug... probably
Seeing this link failure on Windows:
https://github.com/CyberShadow/ae/actions/runs/5574489393/jobs/10184021009#step:8:30
Looks like an MS link SNAFU.
Is there any way I can tell DMD to ignore the presence of MS link
and use the bundled lld-link anyway?
On Tuesday, 23 May 2023 at 13:50:09 UTC, Quirin Schroll wrote:
```
object.Exception@%LOCALAPPDATA%\dub\packages\ae-0.0.3236\ae\sys\d\manager.d(898): Command ["make", "-f",
"win32.mak", "MODEL=32",
On Friday, 3 March 2023 at 01:21:52 UTC, ryuukk_ wrote:
I have some questions:
1. why does it work with LDC?
2. why does it work with DMD when build/link in 2 step?
3. why it doesn't work when DMD is invoked once for build/link
I think these are probably coincidences and the answer can be
On Friday, 3 March 2023 at 01:07:07 UTC, ryuukk_ wrote:
I couldn't figure out dustmite, so i started from 0 and managed
to hit something:
https://github.com/ryuukk/dmd_bug
``Assertion failed: array index out of bounds, file game\app.d,
line 5``
Wich indicates probably TLS problem?
On Wednesday, 30 November 2022 at 01:53:10 UTC, Siarhei Siamashka
wrote:
Rust also appears to be picky about the order of operations:
```Rust
fn main() {
let mut a = [1, 2, 3, 4, 5];
let c = a;
let b = a;
b[1] = 99;
println!("{:?}", b); // [1, 99, 3, 4, 5]
On Wednesday, 30 November 2022 at 01:30:03 UTC, Steven
Schveighoffer wrote:
On 11/29/22 7:50 PM, WebFreak001 wrote:
(note: I don't want to use a template, this way of writing it
has the advantage that the compiler checks all different code
paths for errors, so the errors aren't delayed until
On Thursday, 10 November 2022 at 21:27:28 UTC, Ali Çehreli wrote:
However, ftw performs about twice as fast as dirEntries
Yes, `dirEntries` isn't as fast as it could be.
Here is a directory iterator which tries to strictly not do more
work than what it must:
On Wednesday, 30 November 2022 at 00:40:57 UTC, Vladimir
Panteleev wrote:
On Tuesday, 29 November 2022 at 18:59:46 UTC, DLearner wrote:
Suggestion: it would be clearer if the two concepts were
separated:
1. Convert 'int[] VarArr;' so it produces a straightforward
_value-type_ variable array,
On Tuesday, 29 November 2022 at 18:59:46 UTC, DLearner wrote:
Suggestion: it would be clearer if the two concepts were
separated:
1. Convert 'int[] VarArr;' so it produces a straightforward
_value-type_ variable array, called 'VarArr';
2. Implement a new concept 'int slice Window;' to produce
On Wednesday, 9 November 2022 at 11:55:28 UTC, Guillaume Piolat
wrote:
I've been avoiding void[] for this reason (I mean, void[]
_could_ contain pointers), but I think I'm cargo-culting this?
If I do:
ubyte[] arr = new ubyte[100_000_000];
void[] arr2 = cast(void[]) arr; // will this
On Wednesday, 9 November 2022 at 19:05:58 UTC, Ali Çehreli wrote:
Running the program shows no output; 'a' is not visited as a
directory entry.
That's not what happens for me:
```d
import std.exception;
import std.file;
import std.path;
import std.stdio;
void ls()
{
foreach (e;
On Monday, 17 October 2022 at 05:21:10 UTC, Garrett D'Amore wrote:
I'm happy to announce that I've created what I believe is a
complete, or at least very nearly so, Tree-Sitter grammar for D.
You can find it at https://github.com/gdamore/tree-sitter-d
Congratulations!
Linking to a response
On Friday, 5 August 2022 at 15:36:06 UTC, Rumbu wrote:
The last issues are generated by unpublished changes in the
parser:
Examples:
```d
float z = 85886696878585969769557975866955695.E0; //integer
overflow, I don't see any int
```
The last version where this compiled successfully was D
On Friday, 10 June 2022 at 14:14:27 UTC, Andrey Zherikov wrote:
On Friday, 10 June 2022 at 09:20:24 UTC, Vladimir Panteleev
wrote:
Congratulations on the release. Though there's a good number
of libraries for this task in D already, this solution looks
very complete.
I looked at them when I
On Thursday, 9 June 2022 at 19:08:16 UTC, Andrey Zherikov wrote:
Hi everyone,
I'm glad to announce first major version of
[argparse](https://code.dlang.org/packages/argparse) - a
library for creating command line interface. It took some time
to figure out public API of this library and I
On Tuesday, 17 May 2022 at 16:36:34 UTC, Kenny Shields wrote:
This isn't an open-source project, but I wanted to post this
here for anyone who might be interested in seeing D used for
cross-platform game development. Any questions/comments about
the implementation and design of the game/engine
On Monday, 9 May 2022 at 16:37:15 UTC, H. S. Teoh wrote:
Why is memory protection the only way to implement write
barriers in D?
Well, it's the only way I know of without making it a major
backwards-incompatible change. The main restriction in this area
is that it must continue working with
On Monday, 9 May 2022 at 00:25:43 UTC, H. S. Teoh wrote:
In the past, the argument was that write barriers represented
an unacceptable performance hit to D code. But I don't think
this has ever actually been measured. (Or has it?) Maybe
somebody should make a dmd fork that introduces write
On Sunday, 8 May 2022 at 23:44:42 UTC, Ali Çehreli wrote:
While we are on topic :) and as I finally understood what
generational GC is[1], are there any fundamental issues with D
to not use one?
I implemented one a long time ago. The only way to get write
barriers with D is memory
On Tuesday, 1 March 2022 at 08:12:43 UTC, bauss wrote:
Can't beat the nice integration and ease of access Github
provides, we need stay fresh to attract new younger souls
I sort of agree with that. I usually don't bother reporting
anything because I don't like bugzilla, it would just be much
On Monday, 24 January 2022 at 17:17:28 UTC, Anonymouse wrote:
Indexing is off for the parent directory. What else can I do?
Disable anti-virus.
If that doesn't help, you could try using Sysinternals Process
Monitor to check what is accessing the file.
On Saturday, 4 September 2021 at 07:38:34 UTC, Andre Pany wrote:
The Dustmite condition you are using seems very generic,
therefore this error message can be triggered by various code
constellations. This might be the reasons why Dustmite is
running so long.
Overly generic test conditions
On Saturday, 4 September 2021 at 06:18:52 UTC, JG wrote:
I tried again. What am I doing wrong?
cp source ~/tmp/source
cd ~/tmp/source
dub build --config prog1 2>&1 | grep "collect2: error: ld
returned 1 exit status"
echo $? #produces 0
find . -name *.o -delete
~/d/DustMite/dustmite -j ./ 'dub
On Thursday, 2 September 2021 at 11:20:18 UTC, Vladimir Panteleev
wrote:
One way to get a very rough estimate is to take the square of
the current reduction (.reduced directory), and divide it by
the square of the original source.
I meant the square of the size of the respective directory.
On Thursday, 2 September 2021 at 11:04:12 UTC, JG wrote:
Hi,
We hit a linking error (after upgrading to dub 1.26.0). I
thought I would try to use dustmite to create a reduced error
test case. One week later it is still running (depth 22). I
don't suppose there is anyway of determining when
On Wednesday, 25 August 2021 at 13:30:36 UTC, rushsteve1 wrote:
`trash-d` tries to mimic `rm`'s semantics as much as possible.
It also unifies all the different `trash-*` commands that
`trash-cli` provides into a single one with flags. One of my
goals with `trash-d` was to make a simpler and
On Tuesday, 24 August 2021 at 02:19:58 UTC, rushsteve1 wrote:
https://github.com/rushsteve1/trash-d
A near drop-in replacement for `rm` that uses the Freedesktop
trash bin. Started because an acquaintance `rm -rf`'d his music
folder and I thought there had to be a better way.
Cool! How does
On Saturday, 30 January 2021 at 22:47:39 UTC, Ahmet Sait wrote:
I'm looking for ways to figure out what parts of the code slows
down the compiler other than brute force trial.
You could try some of the tools listed on the wiki for build time
profiling:
On Friday, 23 July 2021 at 18:53:06 UTC, JG wrote:
Any suggestion on how to try and improve the build time.
You could try some of the tools listed on the wiki for build time
profiling:
https://wiki.dlang.org/Development_tools#Build_time_profiling
(intentional bump to aid search results, as
On Thursday, 15 July 2021 at 07:23:31 UTC, Gleb Kulikov wrote:
Gentleman, good afternoon! And what is the reason that the RSS
of Announce Forum has not been working since May? XML is broken
and ends like this:
Hi,
First, please only post announcements in the Announce forum.
The feed is fine
On Wednesday, 30 June 2021 at 03:52:51 UTC, someone wrote:
One of the things I do not like with D, and it causes me to
shoot me on the foot over and over, is the lack of null for
*every* data type. Things like:
If you want to give any type a "null" value, you could use
On Wednesday, 30 June 2021 at 03:15:46 UTC, someone wrote:
Is the following code block valid ?
Comparison with `nan` always results in `false`:
See section 10.11.5:
https://dlang.org/spec/expression.html#equality_expressions
You can use the `is` operator to perform bitwise comparison, or
On Wednesday, 16 June 2021 at 16:38:58 UTC, Atila Neves wrote:
On Wednesday, 16 June 2021 at 15:48:07 UTC, Vladimir Panteleev
wrote:
On Wednesday, 16 June 2021 at 14:40:05 UTC, Atila Neves wrote:
Interested? Please send a CV to dot name> at
Replying for the benefit of forum.dlang.org users,
On Wednesday, 16 June 2021 at 06:28:40 UTC, guest wrote:
STR:
1. open
http://forum.dlang.org/static-bundle/637528586548394375/dlang.org/js/dlang.js+js/dfeed.js
2. press reload (F5 or ctrl+R)
Noticed this too and fixed it a bit ago. It was sending 500
instead of 304, so actually the only
On Wednesday, 16 June 2021 at 16:49:56 UTC, Tejas wrote:
On Wednesday, 16 June 2021 at 16:24:58 UTC, Vladimir Panteleev
wrote:
On Wednesday, 16 June 2021 at 16:15:31 UTC, Tejas wrote:
On Wednesday, 16 June 2021 at 15:48:07 UTC, Vladimir
Panteleev wrote:
Have a look at the "Also via" column
On Wednesday, 16 June 2021 at 16:15:31 UTC, Tejas wrote:
On Wednesday, 16 June 2021 at 15:48:07 UTC, Vladimir Panteleev
wrote:
Replying for the benefit of forum.dlang.org users, for whom
the tags were not visible due to Markdown.
Thank you so much :D
Also, what other ways exist to visit this
On Wednesday, 16 June 2021 at 14:40:05 UTC, Atila Neves wrote:
Interested? Please send a CV to dot name> at
Replying for the benefit of forum.dlang.org users, for whom the
tags were not visible due to Markdown.
Also, what about remote?
On Monday, 14 June 2021 at 18:08:27 UTC, Justin Choi wrote:
Is there any shortcut for unpacking slices like I'd want to do
in a scenario like this?
`info = readln.strip.split;`
`string a = info[0], b = info[1], c = info[2];`
I tried to implement PHP's "list" language construct here, which
*ae* (***a**lmost **e**verything*) is an auxiliary
general-purpose D library. It is used by forum.dlang.org, Digger,
the D documentation auto-tester, and most of my D projects in
general.
Among many things, it implements an asynchronous event loop,
several network protocols, and various
On Friday, 27 November 2020 at 04:08:33 UTC, Q. Schroll wrote:
I think using digger in principle works and I assume the
problems I got aren't Digger's fault, but ae's. Building DMD +
DRuntime failed.
Sorry about this. It was caused by a breaking change in
Druntime's build script:
On Thursday, 19 November 2020 at 04:23:13 UTC, Marcone wrote:
// Function threadingw()
void threadingw(HWND hwn, void delegate() fun) nothrow {
try {
// Function _fun()
extern(Windows)
uint _fun(void * arg){
(*(cast(void delegate()*)
On Monday, 12 October 2020 at 10:24:44 UTC, FreeSlave wrote:
Can this issue overcome somehow?
Why not add a deprecated overload for your function which takes
the old Flag value?
On Monday, 20 July 2020 at 20:55:52 UTC, Steven Schveighoffer
wrote:
I tried redirecting /dev/null to stdin when executing my
application (and I assumed that would pass onto the process
child), but it still asks. What am I doing wrong?
Generically, I think you want to detach the program from
On Tuesday, 14 April 2020 at 07:03:42 UTC, WebFreak001 wrote:
very nice article!
Thank you!
Also for the performance changes: what do the numbers mean in
the diagram there? Is higher better? What exactly is the unit
of these numbers? Should I even read it from top to bottom or
from bottom
On Monday, 13 April 2020 at 18:53:39 UTC, Steven Schveighoffer
wrote:
Very nice article!
Thank you!
Interesting from the animation that it decided that importing
std.stdio can be "reduced" to importing std!
Yes, it's a new minor annoyance for all DustMite users :)
I see that you can
https://github.com/CyberShadow/win32
https://code.dlang.org/packages/win32
This is a repository + dub package which tracks core.sys.windows,
and makes the declarations within available to all platforms.
This is useful if you need to write cross-platform applications
which e.g. read/write BMP
On Tuesday, 31 March 2020 at 02:51:11 UTC, Superstar64 wrote:
How do I generically create an empty associative array?
If you can't pass it by ref, then adding and then removing an
element is the only way I know.
/// Ensure that arr is non-null if empty.
V[K] nonNull(K, V)(V[K] aa)
{
On Tuesday, 31 March 2020 at 04:00:28 UTC, User wrote:
I'd like to convert the following program to 2020 standards
(i.e, replace the foreach block with a one-line code). I've
tried much and I failed.
Here is how I'd do it.
Because the program downloads and then reads the local file
On Monday, 3 February 2020 at 22:01:18 UTC, Anonymouse wrote:
No, C:\Temp\work\dl\git does not exist. :o
OK, that makes sense.
Please try the latest Digger version
(24cd4168956dad382d05984b4b8d37d9e8ebe3ae).
On Monday, 3 February 2020 at 21:44:20 UTC, Anonymouse wrote:
New log: https://pastebin.com/raw/uUMNQjEN
It looks like it fails to execute git (to get the current version
for the build).
I don't know why that fails, as I see C:\Temp\work\dl\git\cmd is
in PATH in the environment that
On Monday, 3 February 2020 at 21:30:57 UTC, Anonymouse wrote:
I was on beta 8. I forced dub to download the latest now
(3.0.0-alpha-9), wiped the work directory and retried, but to
similar results.
The latest is v3.0.0-alpha-11.
Oh, I guess that's not how semantic versioning works. Probably
On Monday, 3 February 2020 at 20:41:00 UTC, Anonymouse wrote:
It doesn't seem to include debugging symbols.
Is your Digger version up-to-date?
https://github.com/CyberShadow/ae/commit/48ee31a3b0d47e52769ee87b0e673034abe4add5
On Thursday, 17 October 2019 at 06:02:33 UTC, Martin Nowak wrote:
Glad to announce the first beta for the 2.089.0 release, ♥ to
the 44 contributors.
http://dlang.org/download.html#dmd_beta
http://dlang.org/changelog/2.089.0.html
As usual please report any bugs at
https://issues.dlang.org
On Wednesday, 25 September 2019 at 11:40:04 UTC, a11e99z wrote:
I had an idea to make CHM help as D-documentation after a post
about man pages popped up
https://thecybershadow.net/d/docs/
https://github.com/dlang/dlang.org/commits/master/chmgen.d
Generates keyword index, navigation as on
On Tuesday, 24 September 2019 at 21:40:47 UTC, Brett wrote:
The only issue is that buggy dynamic code can result if someone
compares the two and it will fail silently.
But, you don't know if the static array actually contains a
null-terminated string (in which case the comparison is a bug) or
On Monday, 23 September 2019 at 23:22:14 UTC, Brett wrote:
I guess you are probably right... I was thinking that it would
compare up to a null terminator. Seems kinda buggy... maybe the
compiler needs to give a warning? After all, compared a fixed
size array with a dynamic array then will
On Monday, 23 September 2019 at 19:14:15 UTC, Brett wrote:
I imagine I could potentially create a separate process that
has a communication layer between it and the D program but I'm
hoping it would be less work.
You're pretty much describing a client-server design. A lot of
software does
On Monday, 23 September 2019 at 20:38:03 UTC, Brett wrote:
cast(wstring)entry.szExeFile == Name
to!wstring(entry.szExeFile) == Name
These all fail. The strings are clearly the same. I can compare
char by char and it works. latest D 2.088. The only thing is
that szExeFile is a static wchar
On Monday, 23 September 2019 at 08:19:35 UTC, Boris Carvajal
wrote:
On Monday, 23 September 2019 at 01:31:03 UTC, Emmanuelle wrote:
Hello. My problem is exactly what it says on the title: my dmd
(windows 7, x64) doesn't seem to have -fPIC:
I think it's not needed. The generated code on
On Sunday, 22 September 2019 at 16:06:04 UTC, Jesse Phillips
wrote:
https://github.com/JesseKPhillips/std.process-example/
I'm wondering if there are any thoughts for simplification. I
don't mean simplify to perform the same end result, but is the
threading and data copies as simple as they
Hi,
This is a D port of a Go package implementing Content-Defined
Chunking:
https://github.com/CyberShadow/chunker
The package contains the following modules:
- chunker.polynomials - implements Pol, a type which represents a
polynomial from F_2[X]. I'm not quite sure what that is, but they
On Tuesday, 27 August 2019 at 17:11:33 UTC, Mike Franklin wrote:
On Tuesday, 27 August 2019 at 12:58:20 UTC, Vladimir Panteleev
wrote:
It will eventually zero in to commit-level accuracy after it's
been running for a while. I cleared the database as the last
time it was running, it was on
On Monday, 26 August 2019 at 18:51:54 UTC, Vladimir Panteleev
wrote:
On Sunday, 25 August 2019 at 13:38:24 UTC, Mike Parker wrote:
The Symmetry Autumn of Code 2019 application selection process
has come to an end. This year, we've got five projects instead
of three. Congratulations to everyone
On Tuesday, 27 August 2019 at 09:08:58 UTC, Mike Franklin wrote:
It's great to see this back up and running. The compile-time
data is quite interesting. Is there any way to identify a
particular offending commit. The commits identified in the data
points on the chart don't seem to be
On Sunday, 25 August 2019 at 13:38:24 UTC, Mike Parker wrote:
The Symmetry Autumn of Code 2019 application selection process
has come to an end. This year, we've got five projects instead
of three. Congratulations to everyone who was selected! You can
read about them and their projects over at
On Tuesday, 20 August 2019 at 11:51:03 UTC, Daniel Kozak wrote:
For that you can use https://dlang.org/phobos/std_file#append
Don't do that. It will reopen and close the file on every
received chunk. Not only is it slow, but if the file is
renamed/moved/deleted while the download is
On Monday, 15 July 2019 at 19:56:29 UTC, David Nadlinger wrote:
(Corollary: This should be fixed in a point release to unbreak
various tooling and dependent build systems.)
Fortunately, these changes still have not appeared in a release,
so we can still fix them. The reason why this
On Monday, 15 July 2019 at 13:27:39 UTC, Mike Franklin wrote:
I asked for input from other developers before moving forward.
They helped me understand that `rt` is where the core language
features are implemented.
Assuming it was the discussion linked in this thread, it did not
seem like
On Monday, 15 July 2019 at 12:42:57 UTC, Mike Franklin wrote:
... and are the exception, not the rule. I believe they should
be moved to `rt`.
BTW, from this discussion it seems to me that you did not have a
good overview of the situation and made a bad decision based on
that. No problem
On Monday, 15 July 2019 at 12:57:46 UTC, Mike Franklin wrote:
On Monday, 15 July 2019 at 12:27:22 UTC, Vladimir Panteleev
wrote:
This isn't exactly true. The restriction is that core should
not *import* rt. Have a look at all the extern(C) definitions
in Druntime - using extern(C) functions
On Monday, 15 July 2019 at 12:42:57 UTC, Mike Franklin wrote:
On Monday, 15 July 2019 at 12:40:50 UTC, Vladimir Panteleev
wrote:
- core.internal.hash contains the implementation of hashing
routines used for associative arrays.
- core.internal.arrayop contains the implementation of array
On Monday, 15 July 2019 at 12:36:14 UTC, Mike Franklin wrote:
Many of the implementations in `rt/array` are templates, so the
entire implementation should be available through object.d, not
just declarations.
The amount of templated code is still finite, otherwise you would
have needed to
On Monday, 15 July 2019 at 12:14:16 UTC, Mike Franklin wrote:
Many of the implementations in `rt/array` require importing or
referencing other implementations in `rt` (e.g. `rt.lifetime`).
If they were moved to `core.internal` they would require
importing `rt` or peeking into `rt` with various
On Monday, 15 July 2019 at 12:14:16 UTC, Mike Franklin wrote:
On Monday, 15 July 2019 at 12:02:35 UTC, Seb wrote:
I think that fits core.internal better than rt. Have you
considered that during said discussion?
The implementations in `rt/array` contain templates that are
ports of runtime
On Monday, 15 July 2019 at 11:48:13 UTC, Anonymouse wrote:
dub run digger -- build "stable + druntime#2675"
sc.ini and dub output at:
https://pastebin.com/jPnh4yEA
By default Digger builds D for 32-bit only. However, it looks
like Dub is trying to build your code targeting the 64-bit
On Monday, 15 July 2019 at 11:33:44 UTC, Mike Franklin wrote:
I discussed that briefly on Slack with a couple other
developers.
My understanding is the `rt` is the language implementation
and `core` is the low level library for users.
The code in `rt/array` are language implementations.
On Monday, 15 July 2019 at 10:27:49 UTC, Anonymouse wrote:
OPTLINK : Warning 9: Unknown Option : OUT
It looks like it's trying to use MS link command-line syntax with
DM OPTLINK.
I'm not sure why that would happen, as Digger creates a complete
sc.ini file containing full paths to all
On Friday, 5 July 2019 at 03:47:20 UTC, Jonathan M Davis wrote:
Yeah. I ran into the same problem with my own build tool. There
wasn't previously an rt folder in the imports. It was all
hidden in the implementation, and my build tool didn't copy it
over, resulting in confusing errors at first
On Thursday, 4 July 2019 at 12:57:43 UTC, Mike Franklin wrote:
The copy should take place when building druntime from the
makefiles. The files to be copied are listed at
https://github.com/dlang/druntime/blob/12bcb73da97a0c26aaf4b943eabd3c25051a89da/mak/COPY#L405-L408 and, for Windows, should
On Wednesday, 22 May 2019 at 01:36:46 UTC, Shigeki Karita wrote:
Recently, I sent a PR [1] in Chroma (syntax highlighter) to
support D. I think my implementation is not perfect. I made
this announcement to ask some experts for help and to ask Dlang
blogger to use this.
Thank you for working
On Friday, 17 May 2019 at 06:25:23 UTC, Suliman wrote:
Waterfox 56.2.9
Oh! I used on my site new js future. It will work after
updating browser.
Waterfox 56.2.9 is currently the latest version of Waterfox.
There is no newer version to update to.
Waterfox uses an older version of Gecko
On Thursday, 16 May 2019 at 20:17:37 UTC, Steven Schveighoffer
wrote:
We do have a nanosecond resolution, and it's just rounded down
to the nearest 10.
For example:
auto d = 15.nsecs;
assert(d == 10.nsecs);
I'm not sure how to feel about this. Maybe there was a better way
to handle
On Thursday, 16 May 2019 at 17:58:52 UTC, Suliman wrote:
Very strange... it’s working for me now even from mobile.
Which browser?
Waterfox 56.2.9
It does work in Chromium.
On Thursday, 16 May 2019 at 17:42:17 UTC, Alex wrote:
I'm not sure if they are failing to block or if they are
blocking what is being opened(and not the original console).
That is, do I need to not open and simply close stdout?
Yes, I see. It won't work because the two libraries are using
On Thursday, 16 May 2019 at 17:18:01 UTC, Alex wrote:
adding
int dup(int) @trusted;
int dup2(int, int) @trusted;
int close(int) @trusted;
int open(in char*, int, ...) @trusted;
Be sure to make them extern(C).
Sorry, I haven't tried it, I'm guessing that it
On Thursday, 16 May 2019 at 17:05:01 UTC, Alex wrote:
One thing you could try is going one level lower, and using
dup() to save the stream to another fd, close() to close the
stdout one, and dup2() to restore the saved fd over the stdout
one.
Unfortunately D doesn't seem to have dup, dup2.
On Thursday, 16 May 2019 at 16:52:22 UTC, Vladimir Panteleev
wrote:
On Thursday, 16 May 2019 at 16:49:35 UTC, Alex wrote:
Why not just use u?
It generally works fine on all the other filesystems
* operating systems
On Thursday, 16 May 2019 at 16:49:35 UTC, Alex wrote:
Why not just use u?
It generally works fine on all the other filesystems, which today
have mostly standardized on UTF-8.
If that is too much trouble then detect the code page and use u
rather than the extended ascii which looks very out
On Thursday, 16 May 2019 at 15:52:05 UTC, Steven Schveighoffer
wrote:
Hecto-nano-second, the smallest representable unit of time in
SysTime and Duration.
The output shouldn't involve the inner workings of the type. It
should be changed to say 10 ns.
If the output is meant for the developer,
On Thursday, 16 May 2019 at 15:19:03 UTC, Alex wrote:
1 - 17 ms, 553 ╬╝s, and 1 hnsec
WTH!! is there any way to just get a normal u rather than some
fancy useless asci hieroglyphic? Why don't we have a fancy M?
and an h?
It's outputting UTF-8, but, your console is not configured to
display
On Thursday, 16 May 2019 at 14:53:14 UTC, Alex wrote:
I have some code that disables the console because some other
code puts junk on it that I don't want to see... then I enable
it.
One thing you could try is going one level lower, and using dup()
to save the stream to another fd, close()
On Monday, 13 May 2019 at 07:40:37 UTC, Johannes Loher wrote:
I still think that we should make them easily available from
either the website or the forums.
On the forum front page, in the right column, you will find an
"Archive" link.
I believe Mike already mentioned that during the AGM.
On Sunday, 7 April 2019 at 05:24:38 UTC, Alex wrote:
Error: template instance `Reflect!(type)` cannot use local
`type` as parameter to non-global template `Reflect(Ts...)()`
mixin(`import `~moduleName!(T)~`;`);
mixin(`alias X = T.`~name~`;`);
super.Reflect!(X);
I realize
On Tuesday, 26 March 2019 at 15:14:03 UTC, Mike Parker wrote:
Long story short, both milestones are nearly complete now (he
hasn't worked on them sequentially, and has done other tasks
besides). He still wants to wait until he completes them before
we payout the $1000 for the milestones.
On Thursday, 21 March 2019 at 16:54:01 UTC, Roman Sztergbaum
wrote:
I would like to get rid of the "ubytes[256]" because I do not
know the size of the data that is comming, I would like to read
the entire buffer that I send at once. Can someone point me?
If you do not know the size of the
On Tuesday, 19 March 2019 at 13:25:27 UTC, Denis Feklushkin wrote:
On Tuesday, 19 March 2019 at 13:20:37 UTC, Vladimir Panteleev
wrote:
On Tuesday, 19 March 2019 at 13:14:52 UTC, Denis Feklushkin
wrote:
/+ dub.sdl:
name "hello_world"
+/
This doesn't seem necessary :)
I add it ~everywhere
On Tuesday, 19 March 2019 at 13:14:52 UTC, Denis Feklushkin wrote:
/+ dub.sdl:
name "hello_world"
+/
This doesn't seem necessary :)
static
assert(isOutputRange!(typeof(stdout.lockingBinaryWriter),
byte));
static
assert(isOutputRange!(typeof(stdout.lockingBinaryWriter()),
byte));
On Monday, 18 March 2019 at 21:09:55 UTC, Michelle Long wrote:
Trying to speed up extracting some files that I first have to
extract using the command line to files then read those in...
Not sure what is taking so long. I imagine windows caches the
extraction so maybe it is pointless?
You
On Friday, 8 February 2019 at 09:28:48 UTC, JN wrote:
I will try. However, one last thing - in the example test
scripts, it runs first with one compiler setting (or D version)
and the second time with the other compiler setting (or D
version). But it looks like the exit code of the first run
1 - 100 of 1503 matches
Mail list logo
