• clayasaurus <clayasaurus gmail.com> Nov 04 2004
• "Walter" <newshound digitalmars.com> Nov 05 2004
• clayasaurus <clayasaurus gmail.com> Nov 05 2004
• Stewart Gordon <smjg_1998 yahoo.com> Nov 08 2004
• "Walter" <newshound digitalmars.com> Nov 09 2004

clayasaurus <clayasaurus gmail.com> writes:

i'm converting a c++ project to D and i'm getting a ton of error messages

"camera.d(35): struct camera.CVector3 no size yet for forward reference"

does anyone know what this could mean? thx.

"Walter" <newshound digitalmars.com> writes:

"clayasaurus" <clayasaurus gmail.com> wrote in message
news:cmfbe5$18sn$1 digitaldaemon.com...
 i'm converting a c++ project to D and i'm getting a ton of error messages

 "camera.d(35): struct camera.CVector3 no size yet for forward reference"

 does anyone know what this could mean? thx.


Try moving the definition of CVector3 before line 35.

clayasaurus <clayasaurus gmail.com> writes:

thx. that seems to work :)

Walter wrote:
 "clayasaurus" <clayasaurus gmail.com> wrote in message
 news:cmfbe5$18sn$1 digitaldaemon.com...
 
i'm converting a c++ project to D and i'm getting a ton of error messages

"camera.d(35): struct camera.CVector3 no size yet for forward reference"

does anyone know what this could mean? thx.


 
 Try moving the definition of CVector3 before line 35.
 
 

Stewart Gordon <smjg_1998 yahoo.com> writes:

clayasaurus wrote:
 i'm converting a c++ project to D and i'm getting a ton of error messages
 
 "camera.d(35): struct camera.CVector3 no size yet for forward reference"
 
 does anyone know what this could mean? thx.


To me, it means DMD still has a few bugs in this area.  Isn't D meant to 
work regardless of the order in which data types are declared?

Stewart.

"Walter" <newshound digitalmars.com> writes:

"Stewart Gordon" <smjg_1998 yahoo.com> wrote in message
news:cmnj69$2ll9$1 digitaldaemon.com...
 clayasaurus wrote:
 i'm converting a c++ project to D and i'm getting a ton of error




 "camera.d(35): struct camera.CVector3 no size yet for forward reference"

 does anyone know what this could mean? thx.


 To me, it means DMD still has a few bugs in this area.  Isn't D meant to
 work regardless of the order in which data types are declared?


D does do a reasonably good job with this, but not 100%.