Different levels of indirection

[onionrack]

I am trying to pass variable arrays from a function, but get the compile error 105 Different levels of indirection. The same code works in Visual C++. Is this me, or a compiler 4.104 fault please? I've tried PCH and PCD with same result:

[PCM programmer]

[tinley]

Thanks PCM P,
I am aware that C is not C++, but the syntax I have used is C ANSI/ISO according to 'C The Complete Reference', so should work.

Can you or anyone suggest a workaround to pass variable arrays please. I don't really want to re-write the function, as it is the standard can_getd() from the CCS can-dsPIC30.c

Thanks!

[FvM]

You're following the bad habbit not to tell, which line of code and partial expression gives the error.

The problem occurs when the "Reference Parameter" argument unsigned int &one is supplied with a
non-constant array element, don't know why. The problem isn't specific to V4.104 however. It's no standard
C Syntax, so I don't use it in my code. You can use a C standard pointer unsigned int *one instead.

P.S.: I understand, that you're problem is in the extensive usage of "reference parameters" in the
CCS supplied can driver. Personally, I would rewrite the driver code.

Furthermore, the problem is a basic restriction of the CCS "reference parameter" concept. It doesn't work
with variable array elements, because it uses an absolute variable address in the function code
instead of a pointer.

[tinley]

Thanks FvM,

Your input gives good insight and at this point I shall modify the CCS can library so it does what I want! There are many badly documented aspects of this 'nearly' C compiler, especially the PCD version, so thanks to this forum and your time!

Sorry for my bad habits... oversight, not intention.

Cheers

[Ttelmah]

CCS, is very close to 'C' (original K&R version). What it misses (still), is getting close to 'ANSI C'....
I'd reckon that 99.5% of C constructs work with CCS, but perhaps only about 90% of ANSI C constructs, especially more 'complex' steps like reference parameters, work 'fully'....
If you stick to original C syntax, CCS is a lot easier to use!...
Some of it is still to do with hardware. In this example, CCS are trying to save complexity in the code, by 'pre-solving' at compile time, the reference parameters. Works well for constant parameters, but makes variable ones effectively a 'no-no'. Advantage smaller code size, but reduces flexibility. :(

Best Wishes

[FvM]

When you say, reference parameter is an ANSI C feature, can tell which clause of the specification defines it? I couldn't find it yet.