Much improved tuple support.

New 'scope' attribute for RAII objects. 'auto' still works the same, but will not for much longer. Use 'auto' for type inference.

http://www.digitalmars.com/d/changelog.html

http://ftp.digitalmars.com/dmd.174.zip

Walter Bright wrote:
> Much improved tuple support.
> 
> New 'scope' attribute for RAII objects. 'auto' still works the same, but will not for much longer. Use 'auto' for type inference.
> 
> http://www.digitalmars.com/d/changelog.html
> 
> http://ftp.digitalmars.com/dmd.174.zip

This is a great release, thank you!

Walter Bright wrote:
> Much improved tuple support.
> 
> New 'scope' attribute for RAII objects. 'auto' still works the same, but will not for much longer. Use 'auto' for type inference.
> 
> http://www.digitalmars.com/d/changelog.html
> 
> http://ftp.digitalmars.com/dmd.174.zip

Documentation for http://www.digitalmars.com/d/declaration.html#AutoDeclaration needs to be updated to reflect the changes to RAII. I couldnt find any updates to the spec grammar either.

Kyle Furlong wrote:
> Walter Bright wrote:
>> Much improved tuple support.
>>
>> New 'scope' attribute for RAII objects. 'auto' still works the same, but will not for much longer. Use 'auto' for type inference.
>>
>> http://www.digitalmars.com/d/changelog.html
>>
>> http://ftp.digitalmars.com/dmd.174.zip
> 
> Documentation for http://www.digitalmars.com/d/declaration.html#AutoDeclaration needs to be updated to reflect the changes to RAII. I couldnt find any updates to the spec grammar either.

http://www.digitalmars.com/d/attribute.html#scope was updated, seems the above page is the only one in need of an update.

Kyle Furlong wrote:
> Walter Bright wrote:
>> Much improved tuple support.
>>
>> New 'scope' attribute for RAII objects. 'auto' still works the same, but will not for much longer. Use 'auto' for type inference.
>>
>> http://www.digitalmars.com/d/changelog.html
>>
>> http://ftp.digitalmars.com/dmd.174.zip
> 
> Documentation for http://www.digitalmars.com/d/declaration.html#AutoDeclaration needs to be updated to reflect the changes to RAII. I couldnt find any updates to the spec grammar either.

In http://www.digitalmars.com/d/template.html,

"A Tuple whose elements consist entirely of types is called a TypeTuple. A Tuple whose elements consist entirely of types is called an ExpressionTuple." should read such that the last line is "...consist entirely of expressions...."

"Walter Bright" <newshound@digitalmars.com> wrote in message news:ejdj7u$da3$1@digitaldaemon.com...
> Much improved tuple support.

Very cool.

One area where type tuples don't work is in place of a base class list. Any chance of supporting this usage?

template ImplementsCore(T ...) {
  ...
}

abstract class Implements(T ...) : T[0 .. $] {
  mixin ImplementsCore!(T);
}

JohnC wrote:
> One area where type tuples don't work is in place of a base class list. Any chance of supporting this usage?
> 
> template ImplementsCore(T ...) {
>   ...
> }
> 
> abstract class Implements(T ...) : T[0 .. $] {
>   mixin ImplementsCore!(T);
> } 

I never thought of that. I'll see if it can be done.

I folded in the changes, thanks.

Walter Bright wrote:
> Much improved tuple support.
> 
> New 'scope' attribute for RAII objects. 'auto' still works the same, but will not for much longer. Use 'auto' for type inference.
> 
> http://www.digitalmars.com/d/changelog.html
> 
> http://ftp.digitalmars.com/dmd.174.zip

"Improved the statement grammar thanks to Stewart Gordon."

Good work on the whole.  However, I'm puzzled by a few issues:

1. At first sight it appears to bear little resemblance to my rewrite. OK, so it implements the distinction between things that introduce a new scope and things that don't, and on closer examination you've taken into account some of the other issues I've raised.  But what's happened to the issue of where a DeclarationStatement or ScopeGuardStatement (fka ScopeStatement) should be legal?

Moving DeclarationStatement and ScopeGuardStatement from NonEmptyStatement into Statement, NoScopeNonEmptyStatement and NoScopeStatement would achieve the same as my version in this respect.

2. You haven't done the necessary updates to

http://www.digitalmars.com/d/version.html

3. You've added

    ;

as a Statement form.  You still haven't told us what the language gains by having it.  OK, so having it in NoScopeStatement simplifies specifying PragmaStatement and LabeledStatement, which are the only things that use it, but in Statement it appears to serve no purpose.

4. Why do ForStatement and ForeachStatement now take a NoScopeNonEmptyStatement as body, rather than a ScopeStatement?

Stewart.

-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/M d- s:-@ C++@ a->--- UB@ P+ L E@ W++@ N+++ o K-@ w++@ O? M V? PS- PE- Y? PGP- t- 5? X? R b DI? D G e++++ h-- r-- !y
------END GEEK CODE BLOCK------

My e-mail is valid but not my primary mailbox.  Please keep replies on the 'group where everyone may benefit.

Walter Bright wrote:
> Much improved tuple support.
> 
> New 'scope' attribute for RAII objects. 'auto' still works the same, but will not for much longer. Use 'auto' for type inference.
> 
> http://www.digitalmars.com/d/changelog.html
> 
> http://ftp.digitalmars.com/dmd.174.zip

You know what's awesome? This works now:
http://paste.dprogramming.com/dpbaqugv.php

That code is a sort of rough breakdown of how Pyd's function wrapping support works. It's actually /understandable/ now.

-- 
Kirk McDonald
Pyd: Wrapping Python with D
http://pyd.dsource.org