On 2014-01-22 13:16, Andrew Edwards wrote:

> That might be the case. I'm following the instructions here:
>
>      https://github.com/D-Programming-Language/installer/tree/master/osx
>
> Last update was over 9 months ago.

I just noticed an error in the Makefile. I'll create a pull request.

-- 
/Jacob Carlborg

I'm getting deprecation warnings inside std.datetime to use "any" instead of "canFind".

Also DMD now warns about using FP operators, such as <>=, for detecting NaN's. What's the rationale for this? One issue with this is that isNaN cannot be used for CTFE.

There is also a build issue that sometimes occurred at the same place in 2.064 in the form of template instantiation failures and now produces linker errors: https://github.com/rejectedsoftware/vibe.d/issues/458

Finally, I'm getting some "recursive alias" errors that I managed to circumvent in previous releases.

I'm going to run dustmite on these two and create bugzilla issues.

On 2014-01-22 13:16, Andrew Edwards wrote:

> That might be the case. I'm following the instructions here:
>
>      https://github.com/D-Programming-Language/installer/tree/master/osx
>
> Last update was over 9 months ago.

https://github.com/D-Programming-Language/installer/pull/44

-- 
/Jacob Carlborg

On 2014-01-21 23:22, Andrew Edwards wrote:
> Due to building an packaging requirements and a need to address the
> concerns of the community, I changed the naming convention for this and
> all future releases.

I'm getting some regressions when compiling Tango. I filed one bug report but having trouble creating a reduced test case for the other one.

The error I get is:

Regex.d(2524): Error: associative array key type TagIndex does not have 'const int opCmp(ref const TagIndex)' member function
Regex.d(3676): Error: template instance tango.text.Regex.TDFA!dchar error instantiating
Regex.d(4420):        instantiated from here: RegExpT!char
Regex.d(4407): Error: tdfa_t.Command is used as a type
Regex.d(4420): Error: template instance tango.text.Regex.RegExpT!char error instantiating

TagIndex looks like this:

struct TagIndex
{
    uint tag, index;
}

And it's used in an associative array:

uint[TagIndex] registers;

-- 
/Jacob Carlborg

On Wednesday, 22 January 2014 at 03:34:40 UTC, Andrew Edwards
wrote:
> On 1/21/14, 5:22 PM, Andrew Edwards wrote:
>
>> Note: An installer is not yet prepared for Windows.
>>
>
> It is now added: ftp://ftp.digitalmars.com/dmd-2.065.b1.exe

This of course is relying on the zip file getting uploaded to
downloads.dlang.org.  You could use the digitalmars urls for
betas, I suppose, since those don't end up on the download site
anyway.  The url template is just a bit further down in the file.

On Wednesday, 22 January 2014 at 13:09:19 UTC, Leandro Lucarella wrote:
> There is a fairly popular de-facto standard for versioning: semver. Yes,
> it is incompatible with Debian (and I guess FreeBSD) but you can make
> it compatible by just changing one character ("-" -> "~").
>
> Since apparently a version naming scheme is needed, does anyone have
> a good reason NOT to use a standard that's easily adaptable to several
> popular distributions?

As Jacob already said, we will either need to go back to a major of 0, or improve our major number almost everytime there is a release.

On 1/22/2014 5:37 AM, Sönke Ludwig wrote:
> I'm getting deprecation warnings inside std.datetime to use "any" instead of
> "canFind".
>
> Also DMD now warns about using FP operators, such as <>=, for detecting NaN's.
> What's the rationale for this? One issue with this is that isNaN cannot be used
> for CTFE.
>
> There is also a build issue that sometimes occurred at the same place in 2.064
> in the form of template instantiation failures and now produces linker errors:
> https://github.com/rejectedsoftware/vibe.d/issues/458

Did you try the -allinst flag?

>
> Finally, I'm getting some "recursive alias" errors that I managed to circumvent
> in previous releases.
>
> I'm going to run dustmite on these two and create bugzilla issues.

On 2014-01-23 10:15, Mathias LANG wrote:

> As Jacob already said, we will either need to go back to a major of 0,
> or improve our major number almost everytime there is a release.

Ruby has just adopted the semantic versioning scheme[1] . They added a fourth digit. The first digit will be the version of the language, the remaining three digits will work as the regular semantic versioning scheme.

[1] https://www.ruby-lang.org/en/news/2013/12/21/semantic-versioning-after-2-1-0/

-- 
/Jacob Carlborg

On Tuesday, 21 January 2014 at 22:22:01 UTC, Andrew Edwards wrote:
> Due to building an packaging requirements and a need to address the concerns of the community, I changed the naming convention for this and all future releases.
>
> The following is our new naming convention:
>
> 	major.minor.qualifier
>
> Examples follow:
>
> 	#.###.b#  ==> 2.065.b1  // beta
> 	#.###.rc# ==> 2.065.rc1 // release candidate
> 	#.###.0   ==> 2.065.0   // initial release
> 	#.###.#   ==> 2.065.1   // hotfix
>
> Consequently, the name for the previously announced beta has changed. Additionally, installers were prepared and made available. They are as follows:
>
> 	ftp://ftp.digitalmars.com/dmd.2.065.b1.zip
> 	ftp://ftp.digitalmars.com/dmd.2.065.b1.dmg
> 	ftp://ftp.digitalmars.com/dmd_2.065.b1-0_i386.deb
> 	ftp://ftp.digitalmars.com/dmd_2.065.b1-0_amd64.deb
> 	ftp://ftp.digitalmars.com/dmd-2.065.b1-0.fedora.i386.rpm
> 	ftp://ftp.digitalmars.com/dmd-2.065.b1-0.fedora.x86_64.rpm
> 	ftp://ftp.digitalmars.com/dmd-2.065.b1-0.openSUSE.i386.rpm
> 	ftp://ftp.digitalmars.com/dmd-2.065.b1-0.openSUSE.x86_64.rpm
>
> For a description of these packages, visit http://dlang.org/downloads.html.
>
> Note: An installer is not yet prepared for Windows.
>
> Regards,
> Andrew

It would be nice, IMHO, to have release information in the same fashion VisualD does it. Check: https://github.com/D-Programming-Language/visuald/releases . Notice that each release has changelog. -Very nice and professional I think.

On Wednesday, 22 January 2014 at 03:43:51 UTC, Andrew Edwards wrote:
> 1) The link for nsisunz.zip per readme.txt does not work.

I wrote the author of the plugin.