Inline Functions

[championx]

Hi! is there a list of all of the "inline" functions?

I'm having trouble to make my code enter on a pic. Recently i discovered that the read_eeprom and write_eeprom are functions that the compiler write inline, so then i make another function that called write_eeprom and read_eeprom and that make the code a lot smaller.

Is there other functions that are coded inline by the compiler?

thanks!

[jeremiah]

Any of the compiler functions that don't require a header file to use (most of them) are going to be "built in", which is different than "inline". If you look at the .h file for your PIC, you'll see them either mentioned in the comments (v4 compilers) or actually forward declared with _bif in front of them (v5 compiler). Aside from that, the manual lists all the functions the compiler has as well.

[championx]

Hi jeremiah, thanks for your answer. Sorry, i think I'm not writing clearly enough. (english is not my native language).

When i talk about "inline" functions I'm talking about that functions that the compiler copies the code every time that you use them, like write_eeprom.

If you do this:

[jeremiah]

In general the compiler chooses to make a function inline or not based on the context of the program you write and the chip you are writing it for. Not all functions are always inline and even those that typically are aren't "always" inline. output_low(PIN_B13) for example will always generate inline code, but change PIN_B13 to a variable and the nature of the function changes and may not be inline.

What chip are you using and what compiler version?

Here is a quick test example for the PIC24FV32KA304. It doesn't generate any inline code for write_eeprom using the 5.044 version compiler

[Ttelmah]

It also changes it's decision, when the memory gets close to full.

An inline function, uses more ROM, but less scratch RAM, and is slightly faster. When there is plenty of ROM, the compiler will inline things 'by default'.