Function declaration order

[Gabriel]

Hi All,

When declaring structs the variables inside are ordered by their size: floats first, then int16s, then int8s and ints1, as needed... right.

So my question is if this also applies to function declarations?

voids first, int16 types, etc...

I've always organized them by functionality/or resource without any issues... but lately I've been using a ton of structs and it got me thinking it might matter here too... and with variable declarations too by extension.

I'd appreciate any "good practices" recommendation here... i have a massive code cleanup going on.

G.
_________________
CCS PCM 5.078 & CCS PCH 5.093

[Ttelmah]

The compiler re-orders the functions to make them fit in the available
memory pages.
The algorithm is 'reasonable', but not 'brilliant'. So (for instance), if you
have a chip that has a particular page size, and allows four pages, then
declare five large functions, though it is actually possible to fit them
(perhaps fitting the two smallest functions into one page), the compiler
may fail to spot this. It gets it to work 99% of the time where it is
possible.

[avatarengineer]

int1 are created from a byte,
therefore whether you have 1 int1 or 8, both conditions use a byte.

[temtronic]

Hmm. perhaps the 'program_name.sym' file has what you need to know ?? Pretty sure it's the one with the RAM and ROM allocations in it ?

Jay