Mainly more bug fixes.

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

This fixed the last of the Interface bugs that I had been seeing.


"Walter" <newshound@digitalmars.com> wrote in message news:c98ju4$17o$1@digitaldaemon.com...
> Mainly more bug fixes.
>
> http://www.digitalmars.com/d/changelog.html
>
>
>
>

On Fri, 28 May 2004 16:52:45 -0700, Walter wrote:

> Mainly more bug fixes.
> 
> http://www.digitalmars.com/d/changelog.html

from the change log:

> typeof(this).member() now does non-virtual call to member().

bad idea, bad sintax.

Ant

Walter wrote:

>Mainly more bug fixes.
>
>http://www.digitalmars.com/d/changelog.html
>  
>
Wow, you implemented my typeof(this) idea, thanks.

-- 
-Anderson: http://badmama.com.au/~anderson/

"J Anderson" <REMOVEanderson@badmama.com.au> wrote in message news:c98uut$g4r$1@digitaldaemon.com...
> Walter wrote:
>
> >Mainly more bug fixes.
> >
> >http://www.digitalmars.com/d/changelog.html
> >
> >
> Wow, you implemented my typeof(this) idea, thanks.

It was inevitable, because this had to work, too:

    class A
    {    void foo() { }
        void bar() { A.foo(); }
    }

isn't typeof(this) a pointer?
shouldn't it be typeof(*this) ?
or am I silly or in C++ land

does this mean if I do

(MyClass*).happy()
it will call the MyClass happy func?

In article <c98uut$g4r$1@digitaldaemon.com>, J Anderson says...
>
>Walter wrote:
>
>>Mainly more bug fixes.
>>
>>http://www.digitalmars.com/d/changelog.html
>> 
>>
>Wow, you implemented my typeof(this) idea, thanks.
>
>-- 
>-Anderson: http://badmama.com.au/~anderson/

hellcatv@hotmail.com wrote:

>isn't typeof(this) a pointer?
>shouldn't it be typeof(*this) ? or am I silly or in C++ land
>  
>
Your living in C++ land.  Remember in C++ you had to use -> if it was a pointer to access a member.  Also remember that all classes in D are pointers.

>does this mean if I do
>
>(MyClass*).happy()
>it will call the MyClass happy func?
>  
>
I think you mean:

(*MyClass).happy();

which will not work as D hides the fact that classes are pointers (actually they are more like references in some respects).

-- 
-Anderson: http://badmama.com.au/~anderson/

Great: "Allow functions that return void to return expressions. " I was for this too BUT:

import std.c.stdio;

class A{}

void F1(int x)
{
 printf("F1(%d)\n",x);
 return new A();
}

void F2(int x)
{
 printf("F2(%d)\n",x);
 return F1(x);
}

int main ( char [] [] args )
{
 F2(100);
}

This code compiles ok. It seams that a function returning void can
now return anything, is it the expected behaviour?
I would expect the return in F1 not to work and the one in F2 to work?


"Walter" <newshound@digitalmars.com> wrote in message news:c98ju4$17o$1@digitaldaemon.com...
> Mainly more bug fixes.
>
> http://www.digitalmars.com/d/changelog.html
>
>
>
>

In article <pan.2004.05.29.02.07.33.528199@yahoo.ca>, Ant says...
>
>On Fri, 28 May 2004 16:52:45 -0700, Walter wrote:
>
>> Mainly more bug fixes.
>> 
>> http://www.digitalmars.com/d/changelog.html
>
>from the change log:
>
>> typeof(this).member() now does non-virtual call to member().
>
>bad idea, bad sintax.
>

agreed (bad syntax) - don't overload every word until it becomes meaningless

What is with void returning expressions? void is for procedures create an "any" type or something similar

Yes, any type can be implicitly converted to void. -Walter

"Ivan Senji" <ivan.senji@public.srce.hr> wrote in message news:c99hap$1f97$1@digitaldaemon.com...
> Great: "Allow functions that return void to return expressions. " I was for this too BUT:
>
> import std.c.stdio;
>
> class A{}
>
> void F1(int x)
> {
>  printf("F1(%d)\n",x);
>  return new A();
> }
>
> void F2(int x)
> {
>  printf("F2(%d)\n",x);
>  return F1(x);
> }
>
> int main ( char [] [] args )
> {
>  F2(100);
> }
>
> This code compiles ok. It seams that a function returning void can
> now return anything, is it the expected behaviour?
> I would expect the return in F1 not to work and the one in F2 to work?
>
>
> "Walter" <newshound@digitalmars.com> wrote in message news:c98ju4$17o$1@digitaldaemon.com...
> > Mainly more bug fixes.
> >
> > http://www.digitalmars.com/d/changelog.html
> >
> >
> >
> >
>
>