On 2017-07-09 21:43, Christian Köstlin wrote:
I wonder if there is any fiber based / fiber compatible UI-Toolkit out
for dlang. The second question is, if it would make sense at all to have
such a thing?
If I recall correctly, vibe.d has some form of integration with the
native GUI event loop
On 2017-07-10 03:52, Patrick wrote:
Hello,
I'm pleased to announce a new java prototype application that is
designed to translate java source into D source. Or any other language
that support package, class, interface, and enum constructs and provides
a built in memory garbage collection.
On 2017-07-07 20:22, Marek wrote:
What do you mean by 'scalability'? Raw tornado or bottle frameworks have
much better results than vibe.d. Python and Ruby have GIL so they can't
use threads in their standard implementations. They have much better
results anyway.
I think that vibe.d didn't
On 2017-07-05 22:12, H. S. Teoh via Digitalmars-d wrote:
Over time, what is considered "idiomatic D" has changed, and nowadays it
seems to be leaning heavily towards range-based code with UFCS chains
using std.algorithm and similar reusable pieces of code.
It's not UFCS per say that causes the
On 2017-07-01 21:11, Damien Gibson wrote:
As well I only intended to use shared libraries not static ones...
Well, you can use shared libraries in two different way, dynamic linking
or dynamic loading.
Dynamic linking is when you declare your external symbols as usual and
you link with
On 2017-07-01 20:13, Damien Gibson wrote:
Hi... A while back i had some issues with making a usable dll file, to
which i did manage to figure out... Though while trying to use it with
C++ i kept getting an error about a corrupted lib file...
Not sure if this is the issue you're having, but if
On 2017-06-28 07:52, Dmitry Solomennikov wrote:
On Wednesday, 28 June 2017 at 05:01:17 UTC, Eugene Wissner wrote:
On Wednesday, 28 June 2017 at 04:41:25 UTC, Dmitry Solomennikov wrote:
Probably if you have serialized data, you convert strings to other
types, so it may be possible to perfom
On 2017-06-27 19:11, H. S. Teoh via Digitalmars-d wrote:
The cardinal rule of color selection: NEVER only set the foreground
color or the background color alone. ALWAYS set both, otherwise you will
get invisible text (or barely-visible text, like yellow on white) on
somebody's terminal, and
On 2017-06-27 23:10, Sönke Ludwig wrote:
Just ruling out a white background would be
a bad idea. I think on macOS that's the default, for example.
Yes, default background color on the default terminal emulator.
--
/Jacob Carlborg
On 2017-06-27 11:54, John Burton wrote:
I'm coming from a C++ background so I'm not too used to garbage
collection and it's implications. I have a function that creates a
std.socket.Socket using new and connects to a tcp server, and writes
some stuff to it. I then explicitly close the socket,
On 2017-06-27 17:24, Steven Schveighoffer wrote:
Yes, Tango solved this by having a separate "finalize()" method. I wish
we had something like this.
Not sure if this is the same, but I remember that Tango had a separate
method called "dispose" that was called if a class was allocated on the
On 2017-06-26 01:24, Adam D. Ruppe wrote:
I actually like anonymous classes. D took it from Java and D has a lot
of other ways to do it too, but I've found anonymous classes to be nice
with using my gui lib... and the only time I see other people talk about
them is wanting to remove them from
On 2017-06-25 17:47, Adrian Matoga wrote:
There are other 32-bit platforms that are going to stay on the market
for a while. 32-bit ARMs won't disappear anytime soon.
Sure, but as I mentioned I mixed up ketmar and Guillaume Piolat and
Guillaume Piolat is using Apple platforms, as far as I
On 2017-06-24 12:53, Mike Parker wrote:
[1] http://derelictorg.github.io/
I noticed you mentioned dylib files on macOS. Might be worth mentioning
frameworks as well.
--
/Jacob Carlborg
On 2017-06-22 17:19, JamesD wrote:
I have several utilities I have used in AutoIT, and I'm enjoying
converting these to the D language with the DWT GUI.
vhdCopy is a GUI wrapper for VboxManage.exe to copy vhd and set GUUID.
This version 2 replaces buttons with a GUI menu that is useful as an
On 2017-06-21 09:28, Walter Bright wrote:
It does work with C on Windows, Linux, OSX, and FreeBSD, and so it works
with -betterC, too.
For example, in C there's "__thread" and in C++ there's "thread_local".
"__thread" doesn't work with all C++ types because it may contain a
non-trivial
On 2017-06-22 00:19, H. S. Teoh via Digitalmars-d wrote:
The code template says:
extern(C) double funcImpl(double x, double y)
But the function pointer type is declared as:
alias FuncImpl = double function(double, double);
Notice the lack of `extern(C)` in the latter. The
On 2017-06-21 17:51, David Nadlinger wrote:
This is not relevant for cross-compilation, as long as you have the
libraries available. You can actually link a D Windows x64/MSVCRT
executable from Linux today if you copy over the necessary libraries.
The question is just how we can make this as
On 2017-06-20 21:59, David Nadlinger wrote:
For Windows, we use the MS C runtime, though, and the legal situation
around redistribution seems a bit unclear.
Musl (or similar) should be available as an alternative. That will make
it easier to cross-compile as well. But I guess MS C runtime is
On 2017-06-20 22:44, Walter Bright wrote:
For a C implementation that doesn't support TLS, using it in D with
-betterC won't work.
I'm thinking more of a C implementation where it *does* work. But
perhaps you're not expected to do anything besides what you can do in C
when it comes to TLS.
On 2017-06-20 23:30, Guillaume Piolat wrote:
Good move from Apple.
I distribute both bitness as Universal Binaries, most probably this will
still work.
Yes, as long as the tools continue to support it.
--
/Jacob Carlborg
On 2017-06-20 16:16, Petar Kirov [ZombineDev] wrote:
I highly recommend watching this talk:
https://www.youtube.com/watch?v=36Ykla27FIo and browsing through this
repo: https://github.com/ionescu007/lxss which reveals many interesting
details about that part of Windows.
Looks interesting.
On 2017-06-20 16:03, Petar Kirov [ZombineDev] wrote:
I highly doubt that ketmar would have any intention of touching macOS
regardless ;)
I somehow mixed up ketmar and Guillaume Piolat (which used to go by the
alias p0nce). My mistake.
--
/Jacob Carlborg
On 2017-06-20 14:11, Guillaume Piolat wrote:
About macOS 32-bit. Am I the only user?
Yes :)
Things are OK now. The older LDCs will work targeting newer macOS 32-bit for a
while I
guess, so maybe 32-bit can be phased out (especially TLS which I don't
use).
I would guess LDC supports it as
On 2017-06-20 13:51, Moritz Maxeiner wrote:
Last time I checked you only needed the Xcode command line tools (which
are small), not the whole thing.
Yes. But I think there are a few things missing, depending on what you
need. There's some LLDB library that is missing from the command line
On 2017-06-20 03:51, Walter Bright wrote:
Is getting a whole lot better:
https://github.com/dlang/dmd/pull/6918
You can now build D executables that do not link in anything from Phobos
- only from the standard C library.
How is TLS handled? I know at least macOS 32bit requires the
On 2017-06-20 03:51, Walter Bright wrote:
Is getting a whole lot better:
https://github.com/dlang/dmd/pull/6918
You can now build D executables that do not link in anything from Phobos
- only from the standard C library.
BTW, how are asserts handled? Isn't assert usually a macro in C?
--
On 2017-06-20 06:54, ketmar wrote:
"...the dubious optimization of no interior pointers..."
this is the ONLY (i emphasise it!) way i were able to make my e-mail and
irc clients to not leak memory, and keep using GC. on 32-bit systems
false pointers *is* a problem, and NO_INTERIOR really
On 2017-06-20 01:52, Vladimir Panteleev wrote:
- More, much more debugging facilities! Integrate Diamond and Valgrind
interoperability.
Don't for get the Clang sanitizers, assuming they work using LDC.
--
/Jacob Carlborg
On 2017-06-20 06:37, ketmar wrote:
it is higly depends of undocumented windows internals, and not portable
between windows versions. more-or-less working implementations of
`fork()` were existed at least since NT3 era, but nobody considered 'em
as more than a PoC, and even next service pack
On 2017-06-20 09:48, Russel Winder via Digitalmars-d-learn wrote:
But there is lots of paid resource in the core Go community which makes
not using "middleware" feasible by providing your own. Also of course
the Go/C interface is not as clean as is the case in D, so the need for
Go-specific
On 2017-06-20 01:29, Steven Schveighoffer wrote:
I may have misspoke. I mean they didn't depend on the library itself. I
think they do depend on the C wrappers.
So for instance, they didn't use FILE *, but instead used
read/write/recv/send.
They did use the Posix and Windows API functions.
On 2017-06-19 11:19, Dejan Lekic wrote:
Why replacing a rock-stable Make with build-system-X that most likely
adds another dependency.
Where did you get the rock-stable part from?
http://forum.dlang.org/post/euslavyxzcaclrpia...@forum.dlang.org
--
/Jacob Carlborg
On 2017-06-17 08:06, Mike B Johnson wrote:
Thanks. At least D has something going on correctly here.
My feeling is, unless DVM works well with windows, that it probably
currently doesn't offer much help. If it does manage the versioning well
and can deal with the environmental issues well then
On 2017-06-16 17:47, Russel Winder via Digitalmars-d wrote:
Most of it is there, but it isn't as slick an experience as say Rust
and Go. It about being a good and proactive downstream for all the
packaging systems (which is mostly there) and having good installers
where needed, mostly there. I
On 2017-06-16 09:53, Mike B Johnson wrote:
DVM [1] is doing some of this.
Cool, does it keep things well organized
It depends on what you definition of organized. DVM is a tool that
allows you to easily install D compilers. It also allows to easily
switch between multiple versions of the
On 2017-06-16 08:30, Russel Winder via Digitalmars-d wrote:
A direct question to Walter and Andrei really.
If someone, let us say Russel Winder, create a CMake/Ninja and/or
Meson/Ninja build for DMD, is there any chance of it being allowed to
replace the Make system?
If the answer is no, then
On 2017-06-16 05:53, Mike B Johnson wrote:
Seriously! D is starting to gain momentum and if things are not
stabilized it's going to slow D down.
1 ==>> The VERY FIRST order of business is very simple:
When a new user goes to start using D for the first time, D is a PITA to
get working! Don't
On 2017-06-14 11:38, Martin Nowak wrote:
Also without a proposed feature list this discussion is somewhat lame.
You only need one, AST macros ;)
--
/Jacob Carlborg
On 2017-06-14 11:04, Rene Zwanenburg wrote:
I've casted void buffers to structs containing bitfields to read
pre-existing binary files, and that worked just fine. I don't see why it
would be different for memory mapped devices. What do yo mean by 'do more'?
This bitfield discussion came up in
It's a bit unfortunate that I found this after DConf. For those that
have a need to create slides/presentation and are tried of PowerPoint or
Keynote. This is the great tool.
Remark [1] is a tool that generates/converts Markdown into slides and
let you view them in the browser. It's really
On 2017-06-14 06:50, Timothee Cour via Digitalmars-d wrote:
eg:
Error: no property 'IF_gray' for type 'ImageFormat'
=>
Error: no property 'IF_gray' for type 'foo.bar.ImageFormat'
and also, why not show where the symbol is defined?
would PR's for that be accepted? is that hard to implement?
On 2017-06-13 13:22, Russel Winder via Digitalmars-d wrote:
Having now got some bits of libdvbv5 usable from D with aid of DStep –
which let's be honest did 90.357% (roughly) of the work – thoughts turn
to maintenance and distribution. So a few questions/comments:
1. Is Deimos "alive and well"
On 2017-06-12 09:00, Jonathan M Davis via Digitalmars-d wrote:
It's true that we don't have to constantly edit the makefiles, so it's not a
constant pain point, but it does come up every time we add or remove any
modules, and the pain in dealing with the makefiles and the time wasted with
them
On 2017-06-11 21:17, Andrei Alexandrescu wrote:
Phobos' posix.mak offers the ability to only run unittests for one module:
make std/range/primitives.test BUILD=debug -j8
... or package:
make std/range.test BUILD=debug -j8
It runs module tests in parallel and everything. This is definitely
On 2017-06-10 00:34, Seb wrote:
Don't worry about that. It's just a computer. As a temporary workaround,
docker might be worth considering.
Wow. Just modify the Makefile.
--
/Jacob Carlborg
On 2017-06-08 09:32, Michael Reiland wrote:
A few questions:
- Is vibe.d the recommended way of doing web work?
Yes.
- Is that book worth purchasing?
Yes.
- Does D have a good library for accessing Postgres? I see several
listed but I don't know what the most stable would be for
On 2017-06-05 23:38, Joseph Rushton Wakeling wrote:
Yup, my instinct is that if a VERSION file needs to exist at all it
should be created during the build process out of `git describe` output.
It's used by DMD to build the version, that is, the output of "dmd
--version". The content of the
On 2017-06-05 13:48, bvoq wrote:
So I ran: dmd -unittest -main -v -L-lgmp -L-lc -g gmp/*
The error seems to stem from: cc dbgio.o -o dbgio -g -m64 -Xlinker
-no_compact_unwind -lgmp -lc -L/usr/local/Cellar/dmd/2.074.0/lib -lgmp
-lgmp -lgmp -lgmp -lc -lphobos2 -lpthread -lm
Full invocation of
The following code does not compile:
void foo(string a) {}
class Base
{
alias bar this;
string bar()
{
return "";
}
}
class Sub : Base {}
void main()
{
auto sub = new Sub;
foo(sub);
}
But if the "alias this" is copied/moved to the subclass it works. Is
this
On 2017-06-05 01:14, bvoq wrote:
The flag -L-lc seems to have been passed to the library.
This is the full error message after running it with dub test --verbose
You need to continue to invoke the sub commands, that is, DMD, Clang and
the linker with the verbose flag (-v) added. There's no
On 2017-06-04 21:52, Andrei Alexandrescu wrote:
What would be the advantage of moving the default into a hook?
The whole idea was to reduce the number of "static if" in the
implementation.
Hook function is defined: "I want to hook this entire operation."
Hook function is not defined: "I
On 2017-06-04 21:24, Paolo Invernizzi wrote:
If I'm not wrong, it also uses a VM, also if there's the availability of
a native code compiler...
If a VM is involved, it's another game...
Yes, it's running on a VM, the Beam.
--
/Jacob Carlborg
On 2017-06-04 20:13, Russel Winder via Digitalmars-d-learn wrote:
On Sun, 2017-06-04 at 20:31 +0300, ketmar via Digitalmars-d-learn
wrote:
maybe 'cause backtrace is called with `bt` command? ;-)
Sadly even using the correct command, I am not getting any data that
helps infer what the
On 2017-06-04 19:05, Patrick Schluter wrote:
buildPath("/usr/bin", "/usr/bin/gcc")
/usr/bin/usr/bin/gcc is obviously wrong.
Says who? It might be exactly what I want. The case that came up is
inside DStep. The user provides a set of files C header to be translated
to D modules. The user
On 2017-06-03 23:45, Andrei Alexandrescu wrote:
One question - current logic decides whether to call e.g. hookOpBinary
vs. perform the default operation followed by onOverflow. How would that
work if both hookOpBinary and onOverflow are defined?
I'm not sure I fully understand without a code
On 2017-06-04 20:15, Joseph Rushton Wakeling wrote:
On Friday, 2 June 2017 at 15:19:29 UTC, Andrei Alexandrescu wrote:
Array bound accesses should be easy to intercept and have them just
kill the current thread.
Ideally, fiber, as well. Probably the real ideal for this sort of
problem is to
On 2017-06-04 08:18, H. S. Teoh via Digitalmars-d wrote:
Ah, but if you want your function to work both at CTFE and runtime, then
why write `if (__ctfe)` in the first place? :-D
Unless, of course, you're optimizing for runtime with something that's
incompatible with CTFE, like inline assembly
On 2017-06-04 20:19, Jakub Szewczyk wrote:
The problem is, it emits completely wrong code whereever a function is
necessary, like in function pointers. I can try to isolate the change to
global-level function declarations only, to make it generate correct
code that doesn't require running two
On 2017-06-04 12:45, Nordlöw wrote:
My gmp-d tests successfully on Linux as
dub test
but on OS X it fails as
Undefined symbols for architecture x86_64:
"free", referenced from:
...
"malloc", referenced from:
...
Any ideas on why?
On 2017-06-04 07:44, Jesse Phillips wrote:
What is your expected behavior? Throw an exception? You can't really
append an absolute path to another.
Of course you can. I expect buildPath("/foo", "/bar") to result in
"/foo/bar". That's how Ruby behaves.
--
/Jacob Carlborg
On 2017-06-04 10:18, Jakub Szewczyk wrote:
Btw, I've manually ported the basic and configuration headers, so that
no mistakes are made, and then used DStep and a modified DStep to
generate the rest of the headers - my modification was only to change
the way function declarations are generated,
On 2017-06-03 23:44, extrawurst wrote:
On Saturday, 3 June 2017 at 17:30:05 UTC, Jakub Szewczyk wrote:
Mono runtime is a cross-platform, open-source alternative to
Microsoft's .NET framework [1], and it can be embedded in other
applications as a "scripting" VM, but with JIT-compilation enhanced
On 2017-06-04 01:10, Jonathan M Davis via Digitalmars-d-announce wrote:
Only new Phobos modules. DIPs have been discussed quite a bit in the
newsgroup, but their decision process has never been democratic. It's always
been a matter of talking Walter into it, which has usually led to stuff
never
On 2017-06-03 20:31, Russel Winder via Digitalmars-d wrote:
But is this sort guaranteed to happen at compile time rather than
runtime?
Yes. It's the context that decides if it occurs at compile time or at
runtime.
Something declared as "static" or "enum" requires that the value can be
I've been looking a bit at the design of the hooks in
std.experimental.checkedint. Due to all hooks being optional there's
quite a few "static if" in the implementation of checkedint to check if
a hook is implemented.
Wouldn't it be simpler if all hooks were required and a default
On 2017-06-02 23:14, Seiji Emery wrote:
The main worry that I have is that this could
somehow wreak havoc with the GC-managed payload pointer, but I'm not
sure.
As long as you cast between different type of delegates I don't think it
would be a problem. The context pointer is always void*
On 2017-06-01 23:08, Robert burner Schadek wrote:
So my idea is to eventually get this library into phobos, write
benchmarks for all functions in phobos, execute the benchmarks for every
merge into master, use gnuplot to display the results on the dlang
webpage, profit.
In Xcode you can
On 2017-06-02 16:17, Mike Parker wrote:
Congratulations are in order for Jared Hanson. Walter and Andrei have
approved his proposal to remove body as a keyword. I've added a summary
of their decision to the end of the DIP for anyone who cares to read it.
In short:
* body temporarily becomes a
Would it be reasonable for the compiler to check for duplicated keys in
an associative array literal where all the keys are known at compile
time? For example:
auto aa = ["foo": 1, "foo": 1];
--
/Jacob Carlborg
On 2017-06-03 16:22, David Nadlinger wrote:
We could also finally fix the frontend to get around this. At DConf
2015, Walter officially agreed that this is a bug that needs fixing. ;)
That would be nice.
--
/Jacob Carlborg
On 2017-06-03 16:12, Russel Winder via Digitalmars-d-learn wrote:
From the manual page on std.path.buildPath:
writeln(buildPath("foo", "bar", "baz")); // "foo/bar/baz"
writeln(buildPath("/foo/", "bar/baz")); // "/foo/bar/baz"
writeln(buildPath("/foo", "/bar")); // "/bar"
I have no
On 2017-06-03 16:03, Nicholas Wilson wrote:
I think an alias template parameter will work here as aliases take
anything(types, literals, symbols).
No, it doesn't work for types:
void foo(alias a)() {}
void main()
{
foo!(int)();
}
Results in:
Error: template instance foo!int does not
On 2017-06-01 23:04, Martin Nowak wrote:
Glad to announce D 2.074.1.
http://dlang.org/download.html
This point release fixes a few issues over 2.074.0, see the changelog
for more details.
http://dlang.org/changelog/2.074.1.html
Any progress on the remaining regressions [1]?
[1]
On 2017-06-02 09:25, Mike James wrote:
Hi,
I get the following errors when trying to build the swtsnippets with the
latest SWT...
This is due to a regression in the compiler [1]. Please use 2.073.x
until this has been fixed.
[1] https://issues.dlang.org/show_bug.cgi?id=17371
--
/Jacob
On 2017-06-01 21:20, Timon Gehr wrote:
There is no such tool.
In this case, Erlang is a pretty good candidate. It's using green
processes that are even more lightweight than fibers. You can have
millions of these processes. All data is process local. If there's a
corruption in one of the
On 2017-06-01 12:13, Steven Schveighoffer wrote:
It just means that D is an inferior platform for a web framework, unless
you use the process-per-request model so the entire thing doesn't go
down for one page request. But that obviously is going to cause
performance problems.
You can do a
On 2017-06-01 20:40, Brad Anderson wrote:
I am curious to hear what changes you'd all like to see made to Phobos that
can't happen because
of backward compatibility.
Perhaps completely asynchronous IO throughout.
--
/Jacob Carlborg
On 2017-06-01 10:25, Ola Fosheim Grøstad wrote:
Even though a stand-alone tool is just as good in theory I think most
developers want as hassle free builds as possible. If one can just point
to the OS include directory and import directly that would be very neat.
Currently DStep will just
On 2017-05-31 18:02, rikki cattermole wrote:
We already do all this, on Linux (and I think OSX too) Phobos+druntime
is built as a shared library by default.
Not on macOS.
--
/Jacob Carlborg
On 2017-05-31 17:50, Ola Fosheim Grøstad wrote:
But you don't have to do that if it is built into the compiler?
Ah, you mean like that. No, that should be necessary if the bindings are
always generated on the fly. My answer was assuming how DStep currently
is working.
--
/Jacob Carlborg
On 2017-05-31 09:09, Jonathan M Davis via Digitalmars-d wrote:
Hmmm. That would make abstract inconsistent with other attributes on a
class, but after messing around with it a bit, it looks like the only effect
that marking a class with abstract has is how many times you get a linker
error
On 2017-05-30 17:50, Swoorup Joshi wrote:
How difficult is it to turn C++ headers usable for D?
Currently DStep doesn't support C++ headers at all. If think it's quite
some work to support that. Of course it's possible to start simple, i.e.
C++ free functions and continue from there.
--
On 2017-05-30 21:42, Ola Fosheim Grøstad wrote:
On Tuesday, 30 May 2017 at 19:12:28 UTC, Jacob Carlborg wrote:
Currently DStep cannot handle #if or #ifdef.
Oh, that is often required…
Yes, but it's very difficult to do.
Say there's some code looking like this:
#ifdef Windows
#include
On 2017-05-30 17:15, Ola Fosheim Grostad wrote:
That's cool! How robust is in practice on typical header files (i.e
zlib and similar)?
I would say ok. I did try to run DStep on zlib.h just now. It got quite
confused when translating the comments. But disabling that it looked a
lot better.
On 2017-05-30 07:14, H. S. Teoh via Digitalmars-d wrote:
OK, this is the 3rd or 4th time somebody asked about this. What exactly
is involved in making a post on the D blog? Hopefully it would not
require too much more effort, because I usually wouldn't have much time
to spend on top of the
On 2017-05-30 14:27, Ola Fosheim Grøstad wrote:
Maybe even turning some macros into functions?
DStep can do that today.
--
/Jacob Carlborg
On 2017-05-30 14:26, Ola Fosheim Grøstad wrote:
What happend to that Calypso project? I suppose libclang also would
allow you to inspect C header-files and then maybe it would be possible
to synthesize Dish bindings from it on the fly? Not that I have given it
much thought.
I did that by
On 2017-05-29 18:08, Russel Winder via Digitalmars-d wrote:
My biggest problem of the moment is libdvbv5 and librtlsdr. DStep
seemingly cannot help as yet.
I know you have reported a few bugs for DStep. Are those all or anything
else that has not been reported yet?
--
/Jacob Carlborg
On 2017-05-22 17:05, Andrei Alexandrescu wrote:
http://dlang.org/blog/2017/05/22/introspection-introspection-everywhere/
-- Andrei
About the custom attributes that are mentioned, like "has acquired a
lock" attribute. This would be a perfect candidate for a UDA and using
the compiler as a
On 2017-05-18 16:24, Ethan Watson wrote:
On Thursday, 18 May 2017 at 13:41:21 UTC, Andre Pany wrote:
I think the 64 bit version of dmd should be the default these days;)
I believe this is a Windows-only problem.
Yes, DMD fir Linux and FreeBSD is shipped in both 32bit and 64bit. Since
I've run into an issue using DCD [1] on macOS where it crashes with the
exception "Unable to set socket option: Invalid argument". This occurs
when DCD calls "accept" on the Socket it's using. Accept will, through
some calls, eventually call "setSock", which will on macOS set the
socket option
On 2017-05-17 12:01, Seb wrote:
There's also the hope that one day SDC or dmd-fe can be used for plugin
development as libdparse and its tools are inherently quite limited due
to a missing semantic analysis phase.
I agree. Although the tools based on libdparse are here today and are
working.
On 2017-05-16 09:39, Anonymouse wrote:
Linker --gc-sections
IIRC that only works with LDC. With DMD it's possible that it removes
sections that are used but not directly referenced.
--
/Jacob Carlborg
On 2017-05-15 23:33, Adam D. Ruppe wrote:
On Monday, 15 May 2017 at 15:40:58 UTC, Walter Bright wrote:
That's why such needs to be turned into a generic module, instead of
constantly being reinvented.
What I'm saying is that it IS a generic module... in fact, there's
several of them:
On 2017-05-15 01:17, Vladimir Panteleev wrote:
No problem, it could only print out the line if the output is a
terminal, same as for how it decides whether to output colors by default.
Ah, that would be fine.
--
/Jacob Carlborg
On 2017-05-14 18:25, Walter Bright wrote:
1. print out the offending line
I hope this one will be optional/configurable. I don't think it
necessary to print the offending line within an editor/IDE. They usually
can already map the error to the offending line.
--
/Jacob Carlborg
On 2017-05-09 16:13, Walter Bright wrote:
I agree. But one inevitably runs into problems relying on valgrind and
other third party tools:
1. it isn't part of the language
2. it may not be available on your platform
3. somebody has to find it, install it, and integrate it into the
dev/test
On 2017-05-12 13:57, rikki cattermole wrote:
I've never used the variable support in dub, its fairly recent.
Yeah two dashes, my bad.
idgen I don't think right now is setup for the argument, but its either
that or find another solution cross platform to change directories.
I think I have it
On 2017-05-12 13:29, rikki cattermole wrote:
May as well, it is a separate artifact from the build process.
I get:
Invalid variable: dmd_PACKAGE_DIR
And I'm not sure about the syntax. Is that supposed to be two dashes?
And I should add an argument to idgen?
--
/Jacob Carlborg
801 - 900 of 3698 matches
Mail list logo
