Possible bug... with TIGCC v0.95 / v0.96b8 in TIGCC Programming Forum

RSS
Email

0 Points

Possible bug... with TIGCC v0.95 / v0.96b8

Author	Comment
Kimbett	Possible bug... with TIGCC v0.95 / v0.96b8	Lead	[-]
Posts: 208 2009-02-01 22:19:11 Reply Quote More My Recent Posts	I am getting the following error: Tables.h: No such file or directory from the following code: #include "tables.h" I can then right click on the above code line and select Open File at Cursor and it opens the file just fine. So I know there is no path issue... It only seems to work if I drop the files in C:\Program Files\TIGCC\Include\C As if "FILENAME" was being treated as <FILENAME> Any ideas? Edit: Changing the code to: #include "../temp/tables.h" And copying tables.h to: C:\Program Files\TIGCC\Include\temp Now it compiles, but right clicking and selecting Open File at Cursor yields a File 'include' Not Found Thanks, Jeff Last Edited By: Kimbett 2009-02-02 01:18:36. Edited 7 times.
	Remove this ad
Kevin Kofler		#1	[-]
Posts: 7177 2009-02-02 02:59:56 Admin Reply Quote More My Recent Posts	Are you on Window$ Vi$ta? If so, try disabling UAC. There's a mystery bug plaguing TIGCC IDE on Vi$ta (but only on some machines for some reason I don't understand) with exactly these symptoms, and at least one person reported that disabling UAC fixes it for them.
Lionel Debroux		#2	[-]
Posts: 3180 2009-02-02 08:42:21 Former Admin Reply Quote More My Recent Posts	We've made available ( http://www.yaronet.com/posts.php?s=117730 ) two ProcessMonitor captures, one that shows the correct behaviour and the other one that shows the incorrect behaviour, but we're at loss about the possible root cause of the problem Last Edited By: Lionel Debroux 2009-02-02 09:28:04. Edited 1 times.
Kimbett		#3	[-]
Posts: 208 2009-02-03 00:00:17 Reply Quote More My Recent Posts	I'm using XP, but I am working around the issue by relocating the .h files to the include/c folder of TIGCC. Of note, changing the file extension from .h to .c seems to cause different behavior. is #include "somefile.h" handled differently than #include "somefile.c"?
Kevin Kofler		#4	[-]
Posts: 7177 2009-02-03 07:21:25 Admin Reply Quote More My Recent Posts	In the IDE, you can only include files which are listed under "Header Files" in your project. .c files can be moved there (drag&drop in the project tree), but it's not recommended.
	Remove this ad
Kimbett		#5	[-]
Posts: 208 2009-02-05 04:30:03 Reply Quote More My Recent Posts	Normally, I wouldn't #include c files, but I'l trying to recompile Tom Nussbaumer's FAT engine and the latest source does it this way. Does including c files have any adverse effects?
Lionel Debroux		#6	[-]
Posts: 3180 2009-02-05 06:17:18 Former Admin Reply Quote More My Recent Posts	> Does including c files have any adverse effects? No, it doesn't. For example, TI-Chess has been using #include "<...>.c" for many years, in order to help the compiler optimizing the code (e.g. inlining of used-only-once functions), without having to put everything into the same source file. Last Edited By: Lionel Debroux 2009-02-05 08:12:02. Edited 2 times.
Kevin Kofler		#7	[-]
Posts: 7177 2009-02-06 21:40:53 Admin Reply Quote More My Recent Posts	#including .c files is bad coding style, .c files are for compilation units, a #included file is a header file. (But putting code in a header file is also bad coding style.) The clean way is to compile your separate modules separately.
Lionel Debroux		#8	[-]
Posts: 3180 2009-02-07 09:55:23 Former Admin Reply Quote More My Recent Posts	> The clean way is to compile your separate modules separately. Er, independent compilation of non-independent source files (the separation was made for consistency and readability purposes) decreases optimization. This is undesirable in speed-critical code such as TI-Chess' engine.c and FAT's fat.c. Tom used #include <...>.c for a reason
	Remove this ad

<< Previous Topic Next Topic >>

Yuku free message boards

Possible bug... with TIGCC v0.95 / v0.96b8

Possible bug... with TIGCC v0.95 / v0.96b8