Thread overview |
---|
August 02, 2004 no property | ||||
---|---|---|---|---|
| ||||
$ dmd hw/HelloGL.d \ -I~/devel/D/DUI/src:~/devel/D/dool/src:~/dmd/src/phobos \ -c -od../obj -op ty = 7 hw/HelloGL.d(19): no property 'setGLCapability' for type 'GLWidget' well, there is a 'setGLCapability' on 'GLWidget' and I used it before. does 'ty = 7' mean something? seems to be part of the compiler message Ant |
August 02, 2004 Re: no property | ||||
---|---|---|---|---|
| ||||
Posted in reply to Ant | On Mon, 02 Aug 2004 15:04:16 -0400, Ant wrote:
> $ dmd hw/HelloGL.d \
> -I~/devel/D/DUI/src:~/devel/D/dool/src:~/dmd/src/phobos \
> -c -od../obj -op
> ty = 7
> hw/HelloGL.d(19): no property 'setGLCapability' for type 'GLWidget'
>
> well, there is a 'setGLCapability' on 'GLWidget'
> and I used it before.
>
> does 'ty = 7' mean something?
> seems to be part of the compiler message
>
> Ant
work around:
move the import to inside the class body.
Of source this seems to be a special situation
that is not defined.
Ant
|
August 25, 2004 Re: no property | ||||
---|---|---|---|---|
| ||||
Posted in reply to Ant | "Ant" <duitoolkit@yahoo.ca> wrote in message news:pan.2004.08.02.21.17.21.367085@yahoo.ca... > On Mon, 02 Aug 2004 15:04:16 -0400, Ant wrote: > > > $ dmd hw/HelloGL.d \ > > -I~/devel/D/DUI/src:~/devel/D/dool/src:~/dmd/src/phobos \ > > -c -od../obj -op > > ty = 7 > > hw/HelloGL.d(19): no property 'setGLCapability' for type 'GLWidget' > > > > well, there is a 'setGLCapability' on 'GLWidget' > > and I used it before. > > > > does 'ty = 7' mean something? It's some debug code, ignore it. > > seems to be part of the compiler message > > > > Ant > > work around: > > move the import to inside the class body. I strongly recommend against doing that. There must be a better solution than that. |
August 25, 2004 Re: no property | ||||
---|---|---|---|---|
| ||||
Posted in reply to Walter | In article <cghlhg$1v1g$2@digitaldaemon.com>, Walter says... > > >> > >> > Ant >> >> work around: >> >> move the import to inside the class body. > >I strongly recommend against doing that. There must be a better solution than that. You know I can't do that, my projects wouldn't compile anymore. (I can't try 0.99 or 0.100 because of another bug) but either is supported or not. I'm not following all D recomendations. particularly the lower case module names. :p If you decide against support it please make sure the forward refs are really fixed (or I'll be at 0.98 for ever). but why shouldn't it be supported? On OO coding I'm going to use the imported symbols only on inside the body of the class (I don't know if it work for subclasses) so it makes perfect sence hat the import is declared inside the class body. People just aren't use to it. Java doesn't need this because (almost) nothing else goes outside class bodies. If you continue recomending against this I'll try to follow the recomendation :( (slowly) (I'm posting this on the D group also) Ant |
August 25, 2004 Re: no property | ||||
---|---|---|---|---|
| ||||
Posted in reply to Ant | "Ant" <duitoolkit@yahoo.ca> wrote in message news:pan.2004.08.02.19.04.16.114678@yahoo.ca... > $ dmd hw/HelloGL.d \ > -I~/devel/D/DUI/src:~/devel/D/dool/src:~/dmd/src/phobos \ > -c -od../obj -op > ty = 7 > hw/HelloGL.d(19): no property 'setGLCapability' for type 'GLWidget' > > well, there is a 'setGLCapability' on 'GLWidget' > and I used it before. > > does 'ty = 7' mean something? > seems to be part of the compiler message > > Ant > > is the code anywhere reachable? |
August 25, 2004 Re: no property | ||||
---|---|---|---|---|
| ||||
Posted in reply to Ben Hinkle | In article <cgiaus$27e7$1@digitaldaemon.com>, Ben Hinkle says... > > >"Ant" <duitoolkit@yahoo.ca> wrote in message news:pan.2004.08.02.19.04.16.114678@yahoo.ca... >> $ dmd hw/HelloGL.d \ >> -I~/devel/D/DUI/src:~/devel/D/dool/src:~/dmd/src/phobos \ >> -c -od../obj -op >> ty = 7 >> hw/HelloGL.d(19): no property 'setGLCapability' for type 'GLWidget' >> >> well, there is a 'setGLCapability' on 'GLWidget' >> and I used it before. >> >> does 'ty = 7' mean something? >> seems to be part of the compiler message >> >> Ant >> >> > >is the code anywhere reachable? ? I'm not sure I understant but here it is: sure, because moving the import declaration to inside the body of the class solve the problem. Ant > > |
Copyright © 1999-2021 by the D Language Foundation