November 25, 2006
Walter Bright escribió:
> Stack class variables, bug fixes.
> 
> http://www.digitalmars.com/d/changelog.html
> 
> http://ftp.digitalmars.com/dmd.175.zip

Wow, how many bugs fixed! Great!

You forgot to add "super" to the specs... partially. :-)

http://www.digitalmars.com/d/expression.html#IsExpression

---
IsExpression:
	is ( Type )
	is ( Type : TypeSpecialization )
	is ( Type == TypeSpecialization )
	is ( Type Identifier )
	is ( Type Identifier : TypeSpecialization )
	is ( Type Identifier == TypeSpecialization )

TypeSpecialization:
	Type
	typedef
	struct
	union
	class
-->                    <-- "super" wants to be a part of this
	interface
	enum
	function
	delegate
---

And it's ok in the table below.
Ary
November 25, 2006
"Walter Bright" <newshound@digitalmars.com> wrote in message news:ek8vrl$5m8$1@digitaldaemon.com...
> Stack class variables, bug fixes.
>
> http://www.digitalmars.com/d/changelog.html
>
> http://ftp.digitalmars.com/dmd.175.zip

Thanks for implementing type tuples as a base class list. Tuples are emerging as an excellent feature.


November 25, 2006
Walter Bright wrote:
> Stack class variables, bug fixes.
> 
> http://www.digitalmars.com/d/changelog.html
> 
> http://ftp.digitalmars.com/dmd.175.zip

But Christmas is still a month away!  Great work :-)


Sean
November 25, 2006
On Sat, 25 Nov 2006 05:14:01 -0800, Lionello Lunesu <lionello@lunesu.remove.com> wrote:

>
> "Walter Bright" <newshound@digitalmars.com> wrote in message
> news:ek8vrl$5m8$1@digitaldaemon.com...
>> Stack class variables, bug fixes.
>
> Damn, and I just figured out how to do that with alloca :)
>
> Very good release. Thanks!
>
> Which reminds me: will "char[varsize] array_on_stack" ever be possible?
>
> L.
>
>


Huh?

void main() {
   char[256] p;
}

Is already allocated on the stack.  What do you mean?

-JJR
November 25, 2006
John Reimer wrote:
> On Sat, 25 Nov 2006 05:14:01 -0800, Lionello Lunesu <lionello@lunesu.remove.com> wrote:
>> Which reminds me: will "char[varsize] array_on_stack" ever be possible?
> 
> Huh?
> 
> void main() {
>    char[256] p;
> }
> 
> Is already allocated on the stack.  What do you mean?

I think he means something more along the lines of:

void foo(size_t bar) {
    char[bar] p;
}
November 25, 2006
Frits van Bommel wrote:
> John Reimer wrote:
>> On Sat, 25 Nov 2006 05:14:01 -0800, Lionello Lunesu <lionello@lunesu.remove.com> wrote:
>>> Which reminds me: will "char[varsize] array_on_stack" ever be possible?
>>
>> Huh?
>>
>> void main() {
>>    char[256] p;
>> }
>>
>> Is already allocated on the stack.  What do you mean?
> 
> I think he means something more along the lines of:
> 
> void foo(size_t bar) {
>     char[bar] p;
> }

It'd be great if we could also:

void foo(size_t bar) {
    char[bar] p = void;
}

to get rid of the initialization (which can take longer than a heap allocation w/ the current GC).
November 25, 2006
Tom wrote:
> Wow, a million bugfixes and a very nice feature... it seems that you didn't saw the sunlight for quite some time. Thank you.

This time of year, there is little sunlight. Nothing to do but work!
November 25, 2006
I'll fix.
November 25, 2006
Walter Bright schrieb am 2006-11-25:
> Stack class variables

Should the following allocate the class on the stack or not?
#
# scope Object o;
# o = new Object;
#

Thomas


November 26, 2006
Walter Bright wrote:
> Tom wrote:
>> Wow, a million bugfixes and a very nice feature... it seems that you didn't saw the sunlight for quite some time. Thank you.
> 
> This time of year, there is little sunlight. Nothing to do but work!

Oh, I always forget that you people in the North don't have sunlight during this time of the year. Here, in Argentina, it's getting hotter every minute. God bless air conditioning :D

--
Tom;