ZEOS AND LAZARUS 0.9.23 SVN 11069 and FPC 2.1.3 WIN32 ERROR
lazarus / 5-Lazarus Extra Components

----------------------------------------------------------------------
leiteiro · 2007-05-04 20:17

with zeos 0.o9.23 and fpc 2.0.4 I can compile zeos package, but with
fpc 2.1.3 from 04-05-2007 (today) I have the following error:

C:\lazarus\components\Other\ZEOS\src\component\ZAbstractRODataset.pas(
3006,90) Fatal: Syntax error, "," expected but ")" found


const
  BaseFieldTypes: array[TFieldType] of TFieldType = (
    ftUnknown, ftString, ftInteger, ftInteger, ftInteger, ftBoolean,
ftFloat,
    ftFloat, ftBCD, ftDateTime, ftDateTime, ftDateTime, ftBytes,
ftVarBytes,
    ftInteger, ftBlob, ftBlob, ftBlob, ftBlob, ftBlob, ftBlob, ftBlob,
ftUnknown,
    ftString, ftString, ftLargeInt, ftADT, ftArray, ftReference,
ftDataSet,
    ftBlob, ftBlob, ftVariant, ftInterface, ftInterface, ftString,
ftTimeStamp, ftFMTBcd );

----------------------------------------------------------------------
antonio · 2007-05-04 20:23

I guess it's a simple syntax error, you are putting a  ")" more on
your code. Click on the message and IDE will show you the line and
position the error occurs.

----------------------------------------------------------------------
Vincent Snijders · 2007-05-05 10:49

leiteiro, maybe fpc 2.1.3 supports more field types and the ZEOS code
needs to be adapted.

----------------------------------------------------------------------
leiteiro · 2007-05-06 10:34

Quote from: "Vincent"leiteiro, maybe fpc 2.1.3 supports more field
types and the ZEOS code needs to be adapted.


Hi Vincent,

I´m a litle newbie, can yor explain ?

----------------------------------------------------------------------
antonio · 2007-05-06 13:43

He says the array can have more fields than those, so the error.
Please have a look at
http://wiki.lazarus.freepascal.org/Zeos_tutorial/pt

----------------------------------------------------------------------
tatamata · 2007-06-12 11:47

Me too, experienced errors when trying to compile Zeos on Lazarus
developer snapshots with fpc 2.1.X.
Also, developer snapshots can't open projects created with Lazarus
0.9.22 (fpc 2.0.4) normally, so I'm afraid whether it will be possible
to migrate existing projects to future versions of Lazarus?
If I develop a serious application using current official versions of
Lazarus based on fpc 2.0.4, would I be able to continue developing
them in fpc 2.1.X versions?

Regards,

Zlatko

----------------------------------------------------------------------
felipemdc · 2007-06-12 14:24

Quote from: "tatamata"If I develop a serious application using current
official versions of Lazarus based on fpc 2.0.4, would I be able to
continue developing them in fpc 2.1.X versions?

Actually 2.1.x are beta versions, you will likely want to use 2.2, the
stable version, when it's released.

ZeosLib will adapt it's code to be compatible with FPC 2.2. This is
normal in any compiler updates. Some libraries need to be updated when
the compiler is updated too.

So, yes, you will be able to migrate to newer lazarus/fpc versions,
after their stable versions are released.

By the way, ZeosLib has an official website and a forum too (google to
find). If you ask there, ZeosLib developers should be able to fix this
problem quickly. If noone warns them that the problem exists, they
will take longer to solve it.

----------------------------------------------------------------------
leiteiro · 2007-06-15 16:04

I solved this with the following:

procedure TZAbstractRODataset.CheckFieldCompatibility(Field:
TField;FieldDef: TFieldDef);

{$IFDEF FPC}
const

  BaseFieldTypes: array[TFieldType] of TFieldType = (
    ftUnknown, ftString, ftInteger, ftInteger, ftInteger,
    ftBoolean, ftFloat, ftFloat, ftBCD, ftDateTime,
    ftDateTime, ftDateTime, ftBytes, ftVarBytes, ftInteger,
    ftBlob, ftBlob, ftBlob, ftBlob, ftBlob,
    ftBlob, ftBlob, ftUnknown, ftString, ftString,
    ftLargeInt, ftADT, ftArray, ftReference, ftDataSet,
    ftBlob, ftBlob, ftVariant, ftInterface, ftInterface,
    ftString, ftTimeStamp, ftFMTBcd   {$ifdef VER2_1_3UP} ,
ftString,ftBlob {$ENDIF} );

{$ELSE}
---------------------------------------------
I olso modified the zeos.inc wtih this lines:


{$IFDEF FPC}

{$IFDEF VER2_1_5}
  {$DEFINE VER2_1_5UP}
  {$DEFINE VER2_1_3UP}
  {$DEFINE VER2_1_1UP}
{$ENDIF}

{$IFDEF VER2_1_3}
  {$DEFINE VER2_1_3UP}
  {$DEFINE VER2_1_2UP}
  {$DEFINE VER2_1_1UP}
{$ENDIF}

{$IFDEF VER2_1_1}
  {$DEFINE VER2_1_1UP}
{$ENDIF}

{$IFDEF VER2_1}
  {$DEFINE VER2_1UP}
{$ENDIF}

{$IFDEF VER2}
  {$DEFINE VER2_UP}
{$ENDIF}



{$ENDIF}






Quote from: "leiteiro"with zeos 0.o9.23 and fpc 2.0.4 I can compile
zeos package, but with fpc 2.1.3 from 04-05-2007 (today) I have the
following error:

C:\lazarus\components\Other\ZEOS\src\component\ZAbstractRODataset.pas(
3006,90) Fatal: Syntax error, "," expected but ")" found


const
  BaseFieldTypes: array[TFieldType] of TFieldType = (
    ftUnknown, ftString, ftInteger, ftInteger, ftInteger, ftBoolean,
ftFloat,
    ftFloat, ftBCD, ftDateTime, ftDateTime, ftDateTime, ftBytes,
ftVarBytes,
    ftInteger, ftBlob, ftBlob, ftBlob, ftBlob, ftBlob, ftBlob, ftBlob,
ftUnknown,
    ftString, ftString, ftLargeInt, ftADT, ftArray, ftReference,
ftDataSet,
    ftBlob, ftBlob, ftVariant, ftInterface, ftInterface, ftString,
ftTimeStamp, ftFMTBcd );