On Monday, 27 July 2015 at 09:04:08 UTC, Martin Nowak wrote:
> On 07/26/2015 11:13 PM, anonymous wrote:
>> 
>> Is std.expermimental.allocator planned for 2.068 ?
>> I see it's still not merged and we already almost in August.
>
> We're trying hard here to meet some deadlines, so things are really simple. If something is ready (reviewed, tested, documented, and merged into stable) it'll end up in a release, otherwise it'll end up in the next release (only 2 month later).
>
> We can't postpone indefinitely just b/c every other person is trying to push through their particular interests.

Yep I see where the energy goes

http://forum.dlang.org/thread/ckjukjfkgrguhfhkdhhj@forum.dlang.org

On Monday, 27 July 2015 at 23:40:28 UTC, anonymous wrote:
> On Monday, 27 July 2015 at 09:04:08 UTC, Martin Nowak wrote:
>> On 07/26/2015 11:13 PM, anonymous wrote:
>>> 
>>> Is std.expermimental.allocator planned for 2.068 ?
>>> I see it's still not merged and we already almost in August.
>>
>> We're trying hard here to meet some deadlines, so things are really simple. If something is ready (reviewed, tested, documented, and merged into stable) it'll end up in a release, otherwise it'll end up in the next release (only 2 month later).
>>
>> We can't postpone indefinitely just b/c every other person is trying to push through their particular interests.
>
> Yep I see where the energy goes
>
> http://forum.dlang.org/thread/ckjukjfkgrguhfhkdhhj@forum.dlang.org

where it' gone....

On Monday, 27 July 2015 at 23:49:34 UTC, anonymous wrote:
> On Monday, 27 July 2015 at 23:40:28 UTC, anonymous wrote:
>> On Monday, 27 July 2015 at 09:04:08 UTC, Martin Nowak wrote:
>>> On 07/26/2015 11:13 PM, anonymous wrote:
>>>> [...]
>>>
>>> We're trying hard here to meet some deadlines, so things are really simple. If something is ready (reviewed, tested, documented, and merged into stable) it'll end up in a release, otherwise it'll end up in the next release (only 2 month later).
>>>
>>> We can't postpone indefinitely just b/c every other person is trying to push through their particular interests.
>>
>> Yep I see where the energy goes
>>
>> http://forum.dlang.org/thread/ckjukjfkgrguhfhkdhhj@forum.dlang.org
>
> where it' gone....

where it's gone. Instead to solve the conflicts...

On Monday, 27 July 2015 at 16:57:24 UTC, jmh530 wrote:
> I thought the next release was to switch to ddmd and wasn't supposed to add a bunch of new features?

That's for the dmd side, doesn't preclude work on druntime or Phobos.

On Monday, 27 July 2015 at 17:12:49 UTC, Joseph Cassman wrote:
> I can understand that. But releases tend to be several months away. And not just two. So this is a bit frustrating.

We're trying to get to a 2 month interval, and delaying work that doesn't meet the deadlines is necessary to achieve this.
I hope that with a more regular interval people will be more aware of the next release and plan their work accordingly.

Am 27.07.2015 um 22:43 schrieb jmh530:
> On Monday, 27 July 2015 at 18:58:33 UTC, Joseph Cassman wrote:
>>
>> Sorry for the following rant but I am frustrated by the poor quality
>> of support for Windows 64 development.
>>
>> <rant>
>>
>
> I understand that frustration. I had some modest problems getting it to
> work with -m64 on my home computer. However, I had bigger problems
> getting Visual D to work. Eclipse wouldn't work with the Java installed
> on my work computer. Coedit wouldn't install on my work computer either
> (I'm not sure how much this is Coedit's fault though, works fine at
> home). I think at home I'm just going to virtualize a Linux session. I
> can dual-boot the machine, but I always find it a hassle if I'm in the
> middle of doing something in Windows and want to play around with D.

I never had issues with VisualD so far. Which version of VisualStudio do you have installed?

64-bit compilation for DMD also works for me for VisualD, as well as when using DUB from the "VS20xx x64 Native Tools Command Prompt" (xx=13 or 15) with the "-a x86_64" switch.

On Monday, 27 July 2015 at 23:40:28 UTC, anonymous wrote:
> On Monday, 27 July 2015 at 09:04:08 UTC, Martin Nowak wrote:
> Yep I see where the energy goes
>
> http://forum.dlang.org/thread/ckjukjfkgrguhfhkdhhj@forum.dlang.org

That has nothing to do with our release.
https://trello.com/b/XoFjxiqG/active

On Monday, 27 July 2015 at 18:58:33 UTC, Joseph Cassman wrote:
> Sorry for the following rant but I am frustrated by the poor quality of support for Windows 64 development.

Try http://rainers.github.io/visuald/visuald/StartPage.html.

> By way of comparison, I can download other languages and run their installer. After that everything just works: linker included. Why do I have to install a MS toolchain just to get 64-bit linking for DMD?

What languages and what linkers are they using?

> I like D a lot. I have been using it for a while. But I have always had trouble with Win64 development. I need that platform for my work. But I will have to dev on Linux again just for 64-bit support. And hope that this can finally get fixed. Although I am real close to just walking away on this one.

On Monday, 27 July 2015 at 18:58:33 UTC, Joseph Cassman wrote:
> I just wasted a lot of time again trying to get Win64 set up on a machine I had to wipe. I had it working for 2.067.1 somehow but was never able to duplicate that on other machines I have. The information at [1] is outdated. Neither the Windows 7 nor 8.1 SDK install a linker for me now for some reason. I had to install VS 2015 to get a 64-bit linker. This fixed the linker not found post installation issue. But then I got a LIBCMT.lib not found issue. I copied it and other library files to the D installation lib64 subdirectory (I couldn't figure out what to modify in the sc.ini file; tried various modifications). Now I am getting a cryptic LNK4229 error that makes no sense to me. At this point I quit.

Depending on Microsoft's libc and linker for 64-bit is an unfortunate dependency and can cause some hassle. An alternative would be appreciated, but I'm not aware of any.
There is some code in the installer, that detects your SDK, but if you installed it after dmd it won't work. Isn't there some feedback about SDKs during installation?

On 2015-07-26 15:55, Martin Nowak wrote:

> BTW, I'd like to phase out the fat 50-60MB combined zip, and add
> tar.xz/gz for linux/freebsd/osx.
> Does anyone still rely on the combined zip?

Yes, DVM does rely on them.

-- 
/Jacob Carlborg