On Tuesday, May 10, 2016 14:51:02 Vladimir Panteleev via Digitalmars-d wrote: > On Tuesday, 10 May 2016 at 14:35:17 UTC, krzaq wrote: > > On Tuesday, 10 May 2016 at 14:26:27 UTC, Vladimir Panteleev > > wrote: > >> You imply that the error message that Druntime generates when > >> it cannot find the DLL is significantly worse than the error > >> message that the OS generates when it cannot find the DLL. > > > > Even if it's better, it's significantly *later*. Once my code > > runs in a production environment I'd really prefer it to not to > > stop over things that could've easily been prevented. > > You can actually still statically link libcurl to the executable > if you so desire. > > Regardless, I'm not sure that we should worry much about the > particular case where you 1) link to libcurl dynamically 2) > distribute an incomplete application with some DLLs missing and > 3) use libcurl late during your application's runtime.
Testing is supposed to fix that sort of thing. And since you _can_ statically link against libcurl if you want to, then you can still get the compile time error, and I really don't see such issues as a viable argument either. I do wish that std.net.curl were a dub package rather than in Phobos, but having issues where you forgot to include libcurl's dll with your binary is a separate issue. - Jonathan M Davis
