On Wednesday, 13 May 2015 at 07:49:26 UTC, Benjamin Thaut wrote:
On Wednesday, 13 May 2015 at 07:41:27 UTC, Logan Capaldo wrote:
If my program only links against DLLs written in D, sure this
is no worse than the static library/version flag situation.
But one of D's features is C and C++
On Wednesday, 13 May 2015 at 11:41:27 UTC, Benjamin Thaut wrote:
On Wednesday, 13 May 2015 at 11:27:18 UTC, Logan Capaldo wrote:
Yes it won't happen for explicit LoadLibrary's and
GetProcAddresses, but COM or other plugin systems is an
example of a situation where many DLLs may expose the
On Wednesday, 13 May 2015 at 13:31:15 UTC, Benjamin Thaut wrote:
On Wednesday, 13 May 2015 at 12:57:35 UTC, Logan Capaldo wrote:
a.dll provides symbol s1
b.dll provides symbol s1
c.dll imports symbol s1 from a.dll, provides symbol s2
d.dll imports symbol s1 from b.dll, provides symbol s3
On Wednesday, 13 May 2015 at 06:17:36 UTC, Benjamin Thaut wrote:
On Tuesday, 12 May 2015 at 17:48:50 UTC, Logan Capaldo wrote:
q could be a completely different type in a.dll vs. c.dll.
Please correct me if I am wrong, but my understanding of how
import libs get used you can't detect this at
On Friday, 8 May 2015 at 05:26:01 UTC, Benjamin Thaut wrote:
I personally would prefer option 2 because it would be easier
to use and wouldn't cause lots of additional maintenance effort.
Any opinions on this? As both options would be quite some work
I don't wan't to start blindly with one
On Monday, 9 March 2015 at 22:15:43 UTC, Ali Çehreli wrote:
You are right. I had the same observation at minute 11:27
below, where I warn against UFCS with assumeWontThrow:
http://www.youtube.com/watch?feature=player_detailpagev=oF8K4-bieaw#t=687
Ali
Sorry, which is right? I know ifThrown
I just became aware of
http://dlang.org/phobos/std_exception.html#.ifThrown . It's neat,
but it seems non-obvious to me how lazy + UFCS should work in
general.
consider
void lazily(T)(lazy T expression)
{
expression();
}
It's clear when saying lazily(a.b().c()); that the whole of
On Monday, 17 November 2014 at 23:14:32 UTC, Vladimir Panteleev
wrote:
I proposed to build Phobos and Druntime with stack frames
enabled:
This is very much worth it in my opinion. Not just for debugging
but being able to profile (sometimes in production, without
needing to recompile with
On Monday, 10 November 2014 at 19:44:05 UTC, Dicebot wrote:
On Monday, 10 November 2014 at 17:48:04 UTC, Sean Kelly wrote:
On Monday, 10 November 2014 at 16:59:47 UTC, Dicebot wrote:
Right now question is, however, are there any legitimate uses
of `extern(C)` in druntime or those all can be
On Monday, 10 November 2014 at 23:02:54 UTC, Steven Schveighoffer
wrote:
On 11/10/14 5:15 PM, Logan Capaldo wrote:
On Monday, 10 November 2014 at 19:44:05 UTC, Dicebot wrote:
On Monday, 10 November 2014 at 17:48:04 UTC, Sean Kelly wrote:
On Monday, 10 November 2014 at 16:59:47 UTC, Dicebot
On Wednesday, 23 July 2014 at 16:07:44 UTC, Andrei Alexandrescu
wrote:
Last (but not least!) talk of DConf 2014.
https://twitter.com/D_Programming/status/491977150694961152
https://www.facebook.com/dlang.org/posts/889844197695929
On Thursday, 10 July 2014 at 20:20:41 UTC, Sean Kelly wrote:
Not currently. Mostly because you're the first person to run
into this issue (or at least to ask about it, as far as I can
recall). Using signals for collection at all is a real sore
point for me--I think it's a terrible but
Apologies in advance if this belongs on the druntime forum, but
it seemed to be full of exclusively automated posts?
I'm looking to integrate D into an existing code base. So far so
good, but I'm concerned that the relatively rare but non-zero use
of SIGUSR1/SIGUSR2 in the code base will, due
13 matches
Mail list logo
