From: Daniel M. German <dmg@uv...>  20070108 22:03:46

Hi Pablo, Pablo> looks good >> #define PANO_PROJECTION_MAX_PARMS 3 Pablo> Why define a fixed number of parameters? >From a usage point of view both implementations are the same: pano_projection_parameter[PANO_PROJECTION_MAX_PARMS]; pano_projection_parameter * parameters; you would use either one as: parameters[0], parameters[1], etc... The advantage is that if we fix the number of parameters at compile time (which we know) then we don't have to allocate and free memory dinamically. Otherwise we would have to worry about disposing them after they are used. Given that the number of parameters is known at compile time, and it is fairly small, I think this makes life easier for the programmer. dmg >> typedef struct >> { >> int projection; >> int maxVFOV; // units in degrees >> int maxHFOV; >> int numberOfParameters; >> // so far we dont have more than 3 parameters >> pano_projection_parameter[PANO_PROJECTION_MAX_PARMS]; Pablo> If an arbitrary number parameters is supported: pano_projection_parameter * parameters; >> } pano_projection_features;  Daniel M. German "One reason that life is complex is that it has a real part and Andrew Koenig > an imaginary part." http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . 