BoostC Inline Functions - Revision history

Russ hensel: /* Inline C -- Some Details */

2009-03-18T01:03:19Z

Inline C -- Some Details

2009-03-17T04:40:21Z

Inline C -- Some Details

2009-03-16T22:31:34Z

#define with Arguments -- Some Details

2009-03-12T02:11:09Z

#define -- Some Details

2009-03-12T01:49:15Z

Links

2009-03-11T02:06:11Z

Reasons

2009-03-11T02:05:35Z

Ways

2009-03-11T02:02:43Z

Inline Details

2009-03-11T01:59:36Z

#DEFINE Details

2009-03-11T01:57:35Z

Ways

← Older revision		Revision as of 01:03, 18 March 2009
Line 57:		Line 57:

	*You can not debug ( source code ) into the function. UPDATE: Actually this is not correct. Debug of inline functions is disabled by default but can be enabled using compiler command line argument -i		*You can not debug ( source code ) into the function. UPDATE: Actually this is not correct. Debug of inline functions is disabled by default but can be enabled using compiler command line argument -i
		+
		+	Comment:
		+
		+	I tried to use an inline function in a .c file and call it from another .c file. It was declared in the .h file. This would not compile. I had to move the entier inline function to the .h file. This caused other reference problems. So if I did this right just adding the inline qualifier may not be enough in some cases. -- This should be checked more carefully.

	== Inline Assmebler Code -- Some Details ==		== Inline Assmebler Code -- Some Details ==

@@ Line 56: / Line 56: @@
 Cons:
-*You can not debug ( source code ) into the function.
+*You can not debug ( source code ) into the function. UPDATE: Actually this is not correct. Debug of inline functions is disabled by default but can be enabled using compiler command line argument -i
 == Inline Assmebler Code -- Some Details ==

← Older revision		Revision as of 22:31, 16 March 2009
Line 40:		Line 40:

	== #define with Arguments -- Some Details ==		== #define with Arguments -- Some Details ==
		+
		+
		+	Still to be written

	== Inline C -- Some Details ==		== Inline C -- Some Details ==

@@ Line 24: / Line 24: @@
 all of a #define must be contained on one line, but a function typically requires several lines.  The lines can be simulated by the required ";" the end of statement marker, but you can still run out of line length.  You can combine different lines by using the line xxxx characer "\" at the end of a line.  This lets you change:
+     if ( a == 0 ) { x = 1; y = 2; }
 to
+     if ( a == 0 ) { \

← Older revision		Revision as of 01:49, 12 March 2009
Line 61:		Line 61:
	== Links ==		== Links ==

		+	[http://publications.gbdirect.co.uk/c_book/chapter2/textual_program_structure.html 2.3. The Textual Structure of Programs]
		+
		+	[http://irc.essex.ac.uk/www.iota-six.co.uk/c/j1_the_c_preprocessor.asp The C Preprocessor]
		+
		+	[http://www.cs.cf.ac.uk/Dave/C/node14.html The C Preprocessor]
		+
		+	[http://publications.gbdirect.co.uk/c_book/chapter7/how_the_preprocessor_works.html 7.2. How the preprocessor works]
		+
		+	[http://en.wikipedia.org/wiki/C_preprocessor C preprocessor From Wikipedia, the free encyclopedia]


	[[Category:BoostC]][[Category:PIC]]		[[Category:BoostC]][[Category:PIC]]

@@ Line 8: / Line 8: @@
 *Using assembler inline  -- this is not an inline function, at least as I am using the term here.
-== Reasons ==
+== Reasons to Use Inline Functions ==
 *Smaller faster code -- sometimes, sometimes not.  ( the first time it is used, your save the code for subroutine linkage, the second time you call you have two copies of the function )

@@ Line 1: / Line 1: @@
 Inline functions are statements that look like functions but do not really call anyting or return, the code is generated right "inline" with the statements before and after the "function call".  There are a couple of different ways to do this, and a couple of different reasons to do it.
-== Ways ==
+== Ways of Creating Inline Functions==
 *Using a #define
 *Using a #define with arguments
 *Using a inline qualifier in the function definition
-*Using assembler inline
+*Using assembler inline  -- this is not an inline function, at least as I am using the term here.
 == Reasons ==

@@ Line 38: / Line 38: @@
 == #define with Arguments -- Some Details ==
-== Inline Details ==
+== Inline C -- Some Details ==
 For this method you qualify the function with the keyword inline.  According to the manual you can do anything you would with any other function.  Perhaps.
@@ Line 52: / Line 52: @@
 *You can not debug ( source code ) into the function.
 == Source Code Using Inline Functions ==

@@ Line 20: / Line 20: @@
 Because there are actually two different versions of the function.
-== #DEFINE Details ==
+== #define -- Some Details ==
-all of a #define must b e contained on one line, but a function typically requires several lines.  The lines can be simulated by the required ";" the end of statement marker, but you can still run out of line length.  You can combine different lines by using the line xxxx characer "\" at the end of a line.  This lets you change:
+all of a #define must be contained on one line, but a function typically requires several lines.  The lines can be simulated by the required ";" the end of statement marker, but you can still run out of line length.  You can combine different lines by using the line xxxx characer "\" at the end of a line.  This lets you change:
@@ Line 35: / Line 35: @@
 --- all this needs to be completed and verified in boostc
 == Inline Details ==