#include caching

Gamestudio Links

Zorro Links

Trading Journey
by M_D. 04/26/24 20:22

M1 Oversampling
by jcl. 04/26/24 11:12

Eigenwerbung
by jcl. 04/26/24 11:08

AUM Magazine

Latest Screens

1 registered members (AndrewAMD), 839 guests, and 5 spiders.

Key: Admin, Global Mod, Mod

Newest Members

Print Thread

Rate Thread

#include caching #457101 12/26/15 01:28 12/26/15 01:28
Joined: Sep 2007 Posts: 101 Luxembourg K krial057 OP Member
krial057 OP Member K Joined: Sep 2007 Posts: 101 Luxembourg	Today I foudn something new in lite-c. Apparently, multiple #inlcude's to the same file get cached in lite-c: Example: print.c file content: Php Code: printf("test"); main.c file content: Php Code: function main() { #include "print.c" #include "print.c" } "test" will only get printed once in this scnario. However changing the code to the following: Php Code: function main() { #include "print.c" #include "./print.c" } "test" will get printed twice. That's all I wanted to say... I know a lot about all the different things lite-c does, but I never knew about this one. Have a nice day!

Re: #include caching [Re: krial057] #457118 12/27/15 10:40 12/27/15 10:40
Joined: Jul 2001 Posts: 6,904 H HeelX Senior Expert
HeelX Senior Expert H Joined: Jul 2001 Posts: 6,904	I didn't tested it, but I would strongly suggest to not rely on that. Good style is to always use #ifndef/#define/#endif guards around your code. You know what that is?

Re: #include caching [Re: HeelX] #457120 12/27/15 13:40 12/27/15 13:40
Joined: Sep 2007 Posts: 101 Luxembourg K krial057 OP Member
krial057 OP Member K Joined: Sep 2007 Posts: 101 Luxembourg	I know what include guards are. But I wanted to achieve exactly the opposite : include a file twice. Why? For X Macros : Code: // File: color_table.h X(red, "red") X(green, "green") X(blue, "blue") // File: main.c #include <stdio.h> #define X(a, b) a, enum COLOR { #include "color_table.h" }; #undef X #define X(a, b) b, char *color_name[] = { #include "color_table.h" }; #undef X int main() { enum COLOR c = red; printf("c=%s\n", color_name[c]); return 0; } Source :http://www.drdobbs.com/the-new-c-x-macros/184401387

Re: #include caching [Re: krial057] #457121 12/27/15 14:37 12/27/15 14:37
Joined: Jun 2009 Posts: 2,210 Bavaria, Germany Kartoffel Expert
Kartoffel Expert Joined: Jun 2009 Posts: 2,210 Bavaria, Germany	That's some weird and inconvenient way to write your code if you ask me... POTATO-MAN saves the day! - Random

Re: #include caching [Re: Kartoffel] #457122 12/27/15 14:57 12/27/15 14:57
Joined: Apr 2007 Posts: 3,751 Canada WretchedSid Expert
WretchedSid Expert Joined: Apr 2007 Posts: 3,751 Canada	It's not unheard of, and can actually help a lot with decreasing the amounts of code you have to write. It's much easier to use the pre-processor to perform copy and paste than doing it yourself and trying to maintain it. Personally I find it looks ugly, but I can see it merits as well. Shitlord by trade and passion. Graphics programmer at Laminar Research. I write blog posts at feresignum.com