If i declare in PBCC 5 an UDT named Point, with members x and y as single,
the compiler protests against this with "mismatch with prior definition".
However, as there is nothing included, there is not supposed to be any prior definition.
If i declare members x and y as Long, the compiler seems perfectly happy,
which suggests that inside PBCC 5 there lives a predefined UDT named Point,
with members x and y as Long.
I could not find anything about this in the help file.
I also checked the issue with PBCC 4, and found that it is specific for PBCC 5.
Should i consider this as a compiler bug, or is there some other explanation ?
Arie Verheul
the compiler protests against this with "mismatch with prior definition".
However, as there is nothing included, there is not supposed to be any prior definition.
If i declare members x and y as Long, the compiler seems perfectly happy,
which suggests that inside PBCC 5 there lives a predefined UDT named Point,
with members x and y as Long.
I could not find anything about this in the help file.
I also checked the issue with PBCC 4, and found that it is specific for PBCC 5.
Should i consider this as a compiler bug, or is there some other explanation ?
Arie Verheul
Code:
#Compile Exe #Dim All #Break On Type Point x As Single y As Single End Type Function PBMain () As Long Local Pt As Point Print Pt.x,Pt.y Pt.x = 10 Pt.y = 15 Print Pt.x,Pt.y WaitKey$ End Function
Comment