Is there some known problem using #module?

[Guest]

Is there some known problem using

[ckielstra]

Post your compiler version number.

Describe the problem you get.

[Guest]

Hi

My project is some "c" files and some "h" files (prototyping). The project is a working project with 3000 lines.

I made a backup and want to make more structure in the files.

I put #module in one of the "c" files and the project still compile and run as expected.

But when applying the #module in one more file some malfunction appear in the project it compile without any problem. I then trying to move the keyword #module longer down in the file and I can then get the project to run. I looked in the list file for some compare and it look like the compiler destroy the printf() function all place...

Solution I just drop the #module keyword.

[ckielstra]

The #module is a new function of the v4 compiler, it is very well possible you have found a bug.

Always mention your compiler version number so it can be checked to be an old and solved problem or is a new bug. Without version number I'm not going to waste time looking into it.

[Guest]

PIC 18x2455 CCS 4.083.

Maybe try to put some #module in your "c" file and make compile test, but you must compare the "list" file.

I think the "c" file you try it on must deal function to other module, and you then need to make some prototyping, before the #module keyword.

[andrewg]

Apart from the prototyping issues already mentioned, the typical problem I get is the compiler putting automatically generated compiler functions into modules, eg the multiply and divide functions.

I've worked around that by having a function outside all the modules that performs the required operations to define the needed functions before the modules have a chance to. The function itself isn't called by anything and so gets optimised away.
_________________
Andrew