Re: pro*C parser bug?

In article <39gqur$mq6_at_tequesta.gate.net> gnd_at_gate.net "Gregory Dora" writes:

> Why does my pro*c precompiler change a VARCHAR declaration?
>
> It turns VARCHAR foo[5000][12]; from the .pc source to
> struct
> {
> char arr[14];
> int len;
> }foo [5000];
> in the generated .c file.
>
> I must have 30 VARCHARS it parses right, but this one it messes up.
> The .c code shows the unparsed VARCHAR foo[5000][12] in the comments
> but messes up the code it generates. Has anyone else had this
> problem?
>
> I am doing a port from a Motorola box running Oracle 6x and Unix to a
> HP running Oracle 7x and Unix.
>
> Thank You,
> Greg Dora
> gnd_at_hopi.gate.net or
> gdora_at_pts.mot.com

Perhaps Pro*C is deciding to have each element of the array start on a 4 byte boundary?

-- 
Paul Beardsell                          SAM Business Systems Ltd
~~~~~~~~~~~~~~                          21 Finn House, Bevenden St,
pbeardsell_at_cix.compulink.co.uk          London, N1-6BN, UK.
psb_at_sambusys.demon.co.uk                (+44 or 0)71 608-2391